Four Distributed Systems Architectural Patterns by Tim Berglund

Developers and architects are increasingly called upon to solve big problems, and we are able to draw on a world-class set of open source tools with which to solve them. Problems of scale are no longer consigned to the web’s largest companies, but are increasingly a part of ordinary enterprise development. At the risk of only a little hyperbole, we are all distributed systems engineers now.
In this talk, we’ll look at four distributed systems architectural patterns based on real-world systems that you can apply to solve the problems you will face in the next few years. We’ll look at the strengths and weaknesses of each architecture and develop a set of criteria for knowing when to apply each one. You will leave knowing how to work with the leading data storage, messaging, and computation tools of the day to solve the daunting problems of scale in your near future.

[@emjay6968]

Tim Berglund is great at giving entertaining talks about complex issues :-D

[@DevoxxPoland]

Agree. One of our favorite speakers.

[@onkarparmar]

Superb talk, seems fresh even after 6 years!

[@lhxperimental]

I had watched this video years ago. Remembered it only halfway through when he made the Slack joke. Facepalm😄

[@angstrom1058]

Funny how all that "hot tech" obsoleted in 6 years.

[@logantcooper6]

Cassandra and Kafka? You're kidding right?

[@petevenuti7355]

Are there any smaller cluster setup that can run a single instance of a single application that's way to large for a single average system? Basically an SSI like kerigrid but more current, something with distributed memory that can handle software meant for extreme high end servers but using a group of ordinary systems. Specific for situations where you can't do redevelopment of the software to taylor it for message passing or other programming techniques to use parallel hardware.

[@tomknud]

When sharding goes horribly wrong!

[@denebgarza]

When sharting goes horribly wrong (always)