Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Get Your Hands Dirty on Clean Architecture

You're reading from   Get Your Hands Dirty on Clean Architecture Build ‘clean' applications with code examples in Java

Arrow left icon
Product type Paperback
Published in Sep 2019
Publisher Packt
ISBN-13 9781839211966
Length 156 pages
Edition 1st Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
Tom Hombergs Tom Hombergs
Author Profile Icon Tom Hombergs
Tom Hombergs
Arrow right icon
View More author details
Toc

Table of Contents (13) Chapters Close

About the Book 1. What's Wrong with Layers? 2. Inverting Dependencies FREE CHAPTER 3. Organizing Code 4. Implementing a Use Case 5. Implementing a Web Adapter 6. Implementing a Persistence Adapter 7. Testing Architecture Elements 8. Mapping Between Boundaries 9. Assembling the Application 10. Enforcing Architecture Boundaries 11. Taking Shortcuts Consciously 12. Deciding on an Architecture Style

How Does This Help Me Build Maintainable Software?

Spring and Spring Boot (and similar frameworks) provide a lot of features that make our lives easier. One of the main features is assembling applications out of the parts (classes) that we, as application developers, provide.

Classpath scanning is a very convenient feature. We only have to point Spring to a package and it assembles an application from the classes it finds. This allows for rapid development, with us not having to think about the application as a whole.

Once the code base grows, however, this quickly leads to a lack of transparency. We don't know which beans exactly are loaded into the application context. Also, we cannot easily startup isolated parts of the application context to use in tests.

By creating a dedicated configuration component responsible for assembling our application, we can liberate our application code from this responsibility (read: "reason for change" – remember the "S" in...

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