Scaling Betsson Tech

Betsson Techs journey into micro services and Docker

Transcript

1. Scaling the gaming platform @Betsson Journey of the monolith Roger Johansson Akka.NET Co-Founder Twitter: @rogeralsing Github: rogeralsing Mail: roger.johansson@betsson.com Github.com/rogeralsing/presentations All material from this presentation
2. ABOUT BETSSON GROUP 1766 Employees (Q2 2016) + 500 tech employees + 40 nationalities 2121 different brands Across Europe, Central Asia & Latin America 41% 563,247 Active players (Q2 2016) 0% 5% 10% 15% 20% 25% 30% 35% 0 500 1 000 1 500 2 000 2 500 3 000 3 500 4 000 2011 2012 2013 2014 2015 H1 2016 SEK m Profitable Growth Revenue EBIT margin 1963 Company founded 2014 Revenue SEK 3,722 m 2015 EBIT SEK 886 m 73% Casino 24% Sportsbook Share of revenue Listed on Nasdaq Large Cap Share of revenue (Q2 2016) Mobile 19.1% Top line CAGR of 19.1% (2012-2015)
3. What to expect from this talk A bit of history on where we came from in terms of architecture Geekery about microservices, service discovery, Docker and .NET Core I will not talk about Akka.NET I am not an Ops guy
4. The Past
5. One Brand, One System Bets10 The Monolith
6. We acquired more brands Bets10 The Monolith NordicBet Betsafe ? ?
7. Scaling the monolith A monolithic application puts all its functionality into a single process… …and scales by replicating the monolith on multiple servers -Martin Fowler, James Lewis
8. Scaling by Instance Instance 2 Brand C Instance 3 Brand D Instance 1 Brand A, B
9. Introducing SOA Instance 1 Instance 2 Instance 3 Customer Gaming Campaigns … Customer Gaming Campaigns … Customer Gaming Campaigns … Still pretty darn big services
10. Challenges?
11. Point to point communication Single Message Producer Single Message Consumer No Redundancy Doesn’t Scale
12. Shared Servers, Noisy Neighbours Instance Customer Gaming Campaigns …
13. Instance Single point of failure… Customer Gaming Campaigns …
14. …Same issue with deployment Instance Customer Gaming Campaigns … Down during deployment
15. Challenges! • Scalability, Elasticity • Isolation • Availability • Deployment
16. The Current
17. Adopting Microservices Customer Bounded Contexts Login Registration Customer Data
18. Scaling Microservices A microservice architecture puts each element of functionality into a separate service… …and scales by distributing these services across servers, replicating as needed -Martin Fowler, James Lewis
19. Scaling Microservices Where are you guys!? I’m over here!
20. Service Discovery Service Registry Publish ”I am A” Publish ”I am B” Service A Service B
21. Service Discovery Service Registry Lookup ”Where is B?” Service A Service B
22. Service Discovery Service Registry Call Service A Service B
23. Service Discovery Service A3 Service A2 Service A1 Service B2 Service B1 Service B3 Service Registry
24. Leetspeak 2014, Niklas Gustavsson/Spotify Service Discovery using DNS
25. Consul Demo https://demo.consul.io/ui/
26. Microphone .NET Consul
27. Microphone Consul .NET Service A Microphone I am A Are you alive? Where is X?
28. Consul enables • Scalability – Locate service instances • Availability – Find healthy instances • Circuit Breaker’ish • (Distributed Configuration)
29. Asp.NET Core Demo Show Asp.NET Core with Microphone
30. The future
31. Server Docker Login Registration Customer Data Isolating services from eachother
32. Demo Docker Compose Docker Compose
33. Cluster Schedulers
34. Cluster Schedulers Server 2 Docker Login Registration Customer Data Server 1 Docker Registration Registration …. Server 3 Docker Login …. ….
35. Putting it all together • Show Rancher UI • Install Consul – Docker Compose • Install Asp.NET Core services • Show Consul UI • Scale Services • Redeploy Services • Integrate with legacy services