Chris Richardson describes how to implement business logic using a domain model that is based on event sourcing. He compares and contrasts a hybrid OO/FP design with a purely functional approach.
Vaclav Petricek discusses how to train models, architect and build a scalable system powered by Storm, Hadoop, Spark, Spring Boot and Vowpal Wabbit that meets SLAs measured in tens of milliseconds.
Mandy Waite shows how to get started with Firebase before walking through a live demo of building a multi-user, collaborative mobile app that provides real-time updates to its users.
Michael Brunton-Spall shows how DevOps-like patterns can be applied on microservices to give the development teams more responsibility for their choices, and much more.
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.
Anil Madhavapeddy describes how to design and build "deploy-and-forget" cloud services that are specialized into unikernels, single-address space virtual machines.
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.
Trisha Gee uses Java 8 streams and lambdas to build an app consuming a real-time feed of high velocity data, using services to make sense of the data, and presenting it in a JavaFX dashboard.
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.
John Davies walks through and demonstrates how to reduce latency while increasing throughput in applications, with demos using Java 8 and lambdas.
Philip Wills believes that thinking about independent services and single responsibility applications rather than microservices can help to clarify the architectural complexity trade-offs.