1 / 17

Large-Scale Distributed Systems

Large-Scale Distributed Systems. Bwin poker - a real world example. Henrik Lagercrantz Senior Systems Architect henrik.lagercrantz@bwin.org. Agenda. About bwin Games and online poker Challenges in a large-scale distributed system The P5 poker engine Q&A. bwin Games. Online gaming

kathy
Download Presentation

Large-Scale Distributed Systems

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Large-Scale Distributed Systems Bwin poker - a real world example Henrik Lagercrantz Senior Systems Architect henrik.lagercrantz@bwin.org

  2. Agenda About bwin Games and online poker Challenges in a large-scale distributed system The P5 poker engine Q&A

  3. bwin Games Online gaming Subsidiary of bwin AG ~400 employees in Sthlm Focus on online poker

  4. Online Poker

  5. Some Numbers 14 million registered customers 45k players online at peak 800k player sessions per day 7 million poker rounds played per day 28 million poker hands dealt per day

  6. Complexity

  7. The Domain Model

  8. Handshake Quiz … Request req = awaitRequest() boolean auth = authenticate(req) if (auth) send(new LoginOk()) activateEncryption() else send(new LoginFailed()) … The Client The Server … send(new LoginRequest(“apa”)) LoginResponse resp = awaitResponse() if (isLoginOk(resp)) activateEncryption() send(new Message(“hello!”)) else print(“doh!”) … What’s wrong with this code?

  9. Requirements • Handle 100k concurrent players • 99.9% availability • Wide range of integration scenarios • Operator diversification • High security standards • Support regulatory constraints • Highly maintainable • …

  10. CAP Theorem • Consistency • Availability • Partition-tolerance

  11. Functional Decomposition

  12. Start decomposing… • Find a table • View ongoing games • Play poker • Chat • Process completed rounds • Route client/server communication • Register for a tournament • Create & schedule a new tournament • …

  13. P5 System Overview

  14. History Service Example

  15. Q&A

  16. Summary • Differentiate between essential complexity and accidental complexity! • Understand the problem domain • CAP theorem – “it’s a trade-off” • Functional decomposition is key!

  17. http://bwingames.se For questions regarding internship, thesis work, etc, contact Jonas Rundberg -jonas.rundberg@bwin.org Also feel free to send me (Henrik) email if you have any questions/thoughts/ideas around the technical stuff – henrik.lagercrantz@bwin.org Henrik Lagercrantz Senior Systems Architect henrik.lagercrantz@bwin.org

More Related