Phil Calcado shares the toolkit and strategy SoundCloud uses to keep its microservices explosion manageable, dealing with operations overhead, DevOps, breaking changes and asynchronous behaviors.
Todd Montgomery describes some common problems that have arisen in protocol design, using examples such as HTTP/2, Aeron, etc., and how the solutions can be applied to microservices.
Sylvia Isler presents a microservices case study and lessons learnt - how VMTurbo took the plunge to evolve its monolithic system architecture into a system based on composable microservices.
Dan North describes a model for thinking about the age of code and argues for replaceability as a first class concern, ending up with something that looks a lot like microservices.
Chris Chedgey explores how “locality of relationship” affects coupling, cohesion, and the width of interfaces, showing structural patterns that increase or decrease complexity.
Philip Wills believes that thinking about independent services and single responsibility applications rather than microservices can help to clarify the architectural complexity trade-offs.
Mini-talks: The Machine Intelligence Landscape: A Venture Capital Perspective. The future of global, trustless transactions on the largest graph: blockchain. Algorithms for Anti-Money Laundering
Diptanu Choudhury discusses the design of Netflix’ distributed scheduler based on Mesos and Titan, focusing on bin packing algorithms, scaling in and out of clusters, fault tolerance, and redundancy.
York Xyander, Bodo Junglas discuss strategies for service discoverability and transparent failover in a microservices architecture, how to achieve zero downtime and an auto-scaling architecture.
Mini-talks on: The Seven Deadly Sins of Microservices. The Importance of Wise Protocol-Layer Semantics in the Design of Microservices. HTTP Nanoservices.
Small sessions on: Deterministic testing in a non-deterministic world. Hash Spreads and Probe Functions. Typesafe Config on Steroids. Real-Time Distributed Event-Driven Computing at Credit Suisse.
Mike Amundsen describes a methodology for designing Web APIs (based on the book "RESTful Web APIs") that allows to map key aspects of a business into a usable, scalable, and flexible interface.