Build Stuff'16 Lithuania

Building a service/Microservice is itself
easy. Scaling it on the cloud is not that hard either but operating,
maintaining and iterating a production large scale service is not just
about linearisation. As Cockcroft points out, telemetry and monitoring
is the most important aspect of building Microservices We discuss 5
patterns that any serious Microservice should have: - Canary (an
endpoint reporting health of underlying dependencies) - IO monitor
(measuring all calls from Microservice to external dependencies) - A
circuit breaker - An ActivityId-Propagator - An exception and short
timeout retry policy Apart from the Microservice buzzword, there is a
saddening lack of understanding of what a successful Microservice
architecture requires in terms of monitoring and telemetry. MTR in
case of a Microservice can be much more than a monolith if these 5
patterns are not in place.