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

MVP

MVP can be considered a pattern evolving from the MVC pattern. MVP originated in the 1990s as a response to the limitations and challenges faced when applying MVC to desktop and web application development.

MVP is built upon the concepts of MVC. The View and the Model concepts are shared between the two patterns, but interactions between the View and the Model have significantly changed.

The major limitation of MVC is the tight coupling between the View and the Controller. It results in a limited ability to test the View and the Controller independently. Also, when the View is complex and has a lot of presentation logic, it becomes difficult to test and maintain.

In addition, any variation or extension to the current View inevitably requires a proportional change in the Controller as the Controller needs to understand all the variations and extensions that exist.

MVP promotes an even more decoupled relationship between the View and the Model by introducing the Presenter...

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