Loading…
This event has ended. View the official site or create your own event → Check it out
This event has ended. Create your own
View analytic
Wednesday, May 24 • 15:00 - 16:00
5 Must-have patterns for your web-scale Microservice

Log in to save this to your schedule and see who's attending!

Feedback form is now closed.
Netflix is actually a log generating application that just happens to stream movies"

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.

Speakers
avatar for Ali Kheyrollahi

Ali Kheyrollahi

A distributed systems practitioner and machine learning enthusiast, Ali currently is a solution architect building web-scale solutions that handles more load than StackOverflow. A performance and scalability junkie, he loves HTTP, API design and business-modelling DDD-style. He i... Read More →


Wednesday May 24, 2017 15:00 - 16:00
Room 6