Build Stuff'16 Lithuania

As the microservice train thunders into town, it is bringing with it an old enemy - the Remote Procedure Call. Libraries like Thrift are being used for client-server communication and no one seems to be looking back to the past to understand why we ran screaming from RPC last time. Drawing on bitter experience of DCOM, .NET remoting and Web Services, and his very British desire for a decent cup of tea, in this talk Ian Cooper will explain the anti-patterns of RPC and look at the alternatives which will ensure your system stays stable and he gets a decent brew.

Moving to a distributed system will solve all your problems and you will be in developer heaven. Right? Not exactly, having hundreds of services doing different things means it's increasingly difficult knowing where exactly production issues are hiding. In this talk Sam Elamin will relate his real life experience working on a distributed system dealing with £100,000 worth of transactions every hour. Sam will cover monitoring and how to develop your features based on how your customers use your platform and, most importantly, business metrics. Sam will cover how to implement metrics in your application and setting up dashboards to gaining visibility into what is happening in your production system right now. We'll also go through some helpful techniques to help you convince your domain experts that gaining this insight is invaluable to keeping your competitive advantage. As an extra treat come and see how JUSTEAT time travels in production, using open source software that can be set up in a matter of days!

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.