Search icon
Subscription
0
Cart icon
Close icon
You have no products in your basket yet
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Get Your Hands Dirty on Clean Architecture - Second Edition

You're reading from  Get Your Hands Dirty on Clean Architecture - Second Edition

Product type Book
Published in Jul 2023
Publisher Packt
ISBN-13 9781805128373
Pages 168 pages
Edition 2nd Edition
Languages
Author (1):
Tom Hombergs Tom Hombergs
Profile icon Tom Hombergs

Table of Contents (18) Chapters

Preface 1. Chapter 1: Maintainability 2. Chapter 2: What’s Wrong with Layers? 3. Chapter 3: Inverting Dependencies 4. Chapter 4: Organizing Code 5. Chapter 5: Implementing a Use Case 6. Chapter 6: Implementing a Web Adapter 7. Chapter 7: Implementing a Persistence Adapter 8. Chapter 8: Testing Architecture Elements 9. Chapter 9: Mapping between Boundaries 10. Chapter 10: Assembling the Application 11. Chapter 11: Taking Shortcuts Consciously 12. Chapter 12: Enforcing Architecture Boundaries 13. Chapter 13: Managing Multiple Bounded Contexts 14. Chapter 14: A Component-Based Approach to Software Architecture 15. Chapter 15: Deciding on an Architecture Style 16. Index 17. Other Books You May Enjoy

The power of constructors

Our input model, SendMoneyCommand, puts a lot of responsibility on its constructor. Since the class is immutable, the constructor’s argument list contains a parameter for each attribute of the class. And since the constructor also validates the parameters, it’s not possible to create an object with an invalid state.

In our case, the constructor has only three parameters. What if we had more parameters? Couldn’t we use the builder pattern to make it more convenient to use? We could make the constructor with the long parameter list private and hide the call to it in the build() method of our builder. Then, instead of having to call a constructor with 20 parameters, we could build an object like this:

We can still let our constructor do the validation so that the builder cannot construct an object with an invalid state.

Sound good? Think about what happens if we have to add another field to SendMoneyCommandBuilder...

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 $15.99/month. Cancel anytime}