Summary
In this chapter, we’ve dived into the meaning of the term architecture and checked out its main variations. We’ve seen why having a clean, maintainable, and scalable architecture is important, and we’ve got some hints on how to achieve it (make sure to dig deeper in the Further reading section). We’ve looked at the main architectural patterns, from the (relatively) simpler ones to the slightly more complex ones designed for larger systems. We’ve also discussed what to watch out for when trying to break the monolith – moving from a monolithic architecture to a microservices one. Speaking of the latter, we’ve taken a quick look at some of the most common bad smells you might encounter. Remember – always keep your spider senses active!
As you close this book, remember that writing good code is not a one-time effort but a continuous commitment to excellence. Act like a craftsman, constantly refining your code to reflect...
