Splitting an application up into multiple independent services can be a good way to keep it scaling and ensure stability and developer productivity in larger, growing teams. But just splitting the codebase, creating APIs and deploying the code on some servers is not enough, somehow your services need to know where and how other services are accessible. Classical approaches like hardcoding everything in every service or having a central load-balancer can quickly lead to problems in terms of scalability and maintainability. In this talk I'll show how we at ResearchGate tackled this challenge. With the help of tools like Consul and haproxy we created a setup that allows us to quickly boot and shutdown services. This ensures that all servers are utilized optimally and load spikes can be reacted upon quickly and automatically.


Comments are closed.

Herberto Graca at 14:27 on 1 Jul 2017

Excellent talk!
The speaker knew what he was talking about by his own experience, the subject is cutting edge and the talk had the right granularity/depth.
Best talk so far!

Very informative. A practical view on the subject.

Marc Hagen at 16:03 on 1 Jul 2017

I like the style of presenting and learned allot about kubernetes and cluster scaling. It was really focused on kubernetes but still learned allot and also some really useful tools.

Tim Huijzers at 18:08 on 3 Jul 2017

Learn about a great set of tools and when to use them.

Great talk
Very informative, showing a lot of features/topics without diving very deep into them!

Arnout Boks at 15:45 on 7 Jul 2017

Loads of useful information packed into a 45-min talk. I liked how most of the content was backed by practical experience, and how it showed an evolution from one architecture to another. Great overview of a (microservices) architecture anno 2017.