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 guide to effective pair-programming
«best programs and designs are done by pairs, because you can criticise each other, and find each others errors, and use the best ideas.»
A catalog of patterns to better understand, communicate, and teach the design of distributed systems