architect (microservices), Cloud architect (GCP) • Cover the how, the what, the where and the why • Let’s talk about practical steps on improving microservice systems
under the control of a single team • Services are usually deployed together • The effort around deployment and orchestration overtakes the effort of developing the services
Every team gets the same number of services • Teams are very protective of their services • The services don’t seem to belong together by any other metric aside from belonging to the same team
Stabilize external interfaces • Use contract testing to catch changes early on • Communicate but don’t blame • Defensive programming, built-in resiliance