Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Software Architecture with Kotlin

You're reading from   Software Architecture with Kotlin Analyze, combine, and terraform various architecture styles for sustainable and scalable software

Arrow left icon
Product type Paperback
Published in Dec 2024
Publisher Packt
ISBN-13 9781835461860
Length
Edition 1st Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
Mr. Jason Chow Mr. Jason Chow
Author Profile Icon Mr. Jason Chow
Mr. Jason Chow
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

Preface 1. Chapter 1: The Essence of Software Architecture 2. Chapter 2: Principles of Software Architecture FREE CHAPTER 3. Chapter 3: Polymorphism and Alternatives 4. Chapter 4: Peer-to-Peer and Client-Server Architecture 5. Chapter 5: Exploring MVC, MVP, and MVVM 6. Chapter 6: Microservices, Serverless, and Microfrontends 7. Chapter 7: Modular and Layered Architectures 8. Chapter 8: Domain-Driven Design (DDD) 9. Chapter 9: Event Sourcing and CQRS 10. Chapter 10: Idempotency, Replication, and Recovery Models 11. Chapter 11: Auditing and Monitoring Models 12. Chapter 12: Performance and Scalability 13. Chapter 13: Testing 14. Chapter 14: Security 15. Chapter 15: Beyond Architecture 16. Index 17. Other Books You May Enjoy

Optimize performance now or later?

Engineers and architects often face the question of whether performance should be optimized now or later. This happens from the early stages of system design to already established production systems.

We all know optimizing performance is crucial, but whether to prioritize it from day one isn’t a simple binary question.

You may have heard of someone who said “Premature optimization is the root of evil.” The statement itself is theatrical, but there are some merits in it.

You may also have heard a quote saying, “Make it work, make it right, make it fast.” This was coined by software engineer Kent Beck.

So, what would be the consequences if a system is optimized prematurely, or if we reverse the order to “make it fast” too early?

Spending too much time on performance improvements before understanding user behaviors and requirements can lead to wasted effort. Moreover, it creates an unnecessarily...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image