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.

Van Belle Jonathan (Grummfy) at 18:15 on 27 Jan 2017

very intresting, learn a lot of stuff. but perhaps the talk can give a bit more to take home.

Learned a lot of new tools, found out about possible solutions to a few problems I'm trying to tackle.
Overall great value for me.

Iamabot at 13:43 on 28 Jan 2017

Did not enjoy the fact that you made my coworker climax multiple times during the talk and went to the bathroom for an hour after. Apart from that this talk was legendary and should be mandatory in every team. I am now off to build you a shrine.

Thijs at 13:50 on 28 Jan 2017

Great talk, great build up, good pace and examples.

For me, this was one of the best talks of the conference. It was very structured, detail-rich and to the point. I really like your style of presenting content! This talk makes me want to invest (more) time in everything around docker infrastructure.

Anonymous at 16:08 on 30 Jan 2017