Martin Lippert and John Arthorne demo the creation of a cloud service with Flux, connecting it to a running Flux environment, and implement some basic features for a sample language.
Philip Wills believes that thinking about independent services and single responsibility applications rather than microservices can help to clarify the architectural complexity trade-offs.
Benjamin Hindman discusses Apache Mesos, focusing on the Mesos API and how the primitives provided by Mesos can make it easier to build new stateful services and frameworks.
Annalisa Sarasini talks about how industry standards, open source, HTML5 and hosted services are today leveraged by leading buy and sell side firms when implementing single and cross asset solutions.
Niklas Gustavsson presents Spotify's 2-layer services, and how the UNIX philosophy of composing components that does a single thing well works on a greater scale.
Dustin Huptas, Andreas Schmidt present some of the operational challenges met when dealing with microservices, and offer solutions from the field of automation and service discovery.
Caoilte O'Connor explains how and when the Domain Service Aggregator Archetype can help, using the architectural evolution of "Video on Demand" in a broadcast company as a working example.
Shobana Radhakrishnan shares details about best practices adopted in implementing API integration with third party services, how to manage change and deal with failures.
Caitie McCaffrey does an overview of Orleans, the challenges faced when building the Halo 4 services, and why the Actor Model and Orleans in particular were utilized to solve these problems.
Rachel Reese sees reactive services and functional languages as a natural pair, demonstrating how functional concepts such as mailboxes and async workflows can help one craft reactive services.
Brian Troutwine examines how functional programming and other concepts championed by Erlang can yield reactive services with just a change in thinking and a different approach to design.
Steve Pember discusses the tenants of the Reactive Pattern and the importance of moving away from Monolithic to Reactive architectures.