11–20 of 29 posts
Patterns of Enterprise Application Architecture, Martin Fowler, and Enterprise Integration Patterns, Gregor Hohpe. both predate microservices, and both are still very useful today.
Patterns of Enterprise Application Architecture, Martin Fowler, and Enterprise Integration Patterns, Gregor Hohpe. both predate microservices, and both are still very useful today.
This may sound like I am a complete idiot, but I sincerely think that reading works like the Tao Te Ching may help more than reading books on software architecture. There are still many new ways of architecture to be found. For example, making software with an extension language could result in way better systems than a system envisioned by a customer who has no clue about computers. But unfortunately, it is often a…
Good architecture tends to break up complexity into common building blocks, and avoiding patterns that might cause instability or failure. Or seeing the cause of the instability and then fixing it. IOW, there's really no need to recreate the wheel....
Over time, as you get good at it, you'll see the exact same patterns over and over again, so rather than need to experiment with new technologies or software architectures, you can just reach into your experience and bring things out you know work already.
I'd recommend Clean Architecture by Robert Martin.
Here is a blog post from Robert C. Martin about microservices and clean architecture: https://blog.cleancoder.com/uncle-bob/2014/10/01/CleanMicros...
So: 1) Read classic books about monolith software. 2) Read decent books about microservices approach.