An in-depth description of the microservice style of architecture. Applications designed as suites of independently deployable services, governed in a decentralized manner.
Going directly to a microservices architecture is risky, so consider building a monolithic system first. Split to microservices when, and if, you need it.
There are problems with the centralized data lake. A future data mesh needs domains, self-service platforms, and product thinking.
A catalog of patterns to better understand, communicate, and teach the design of distributed systems
To be successful at digital transformation you need to optimize the key feedback loops in your software engineering organization