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.
Jeff Scott Brown talks about the Grails 2 features and functionality related to building RESTful services.
John Bunting talks about different services Tumblr has built and how their architecture helps them be fault tolerant as they continue to grow.
Anthony Molinaro discusses the challenges of troubleshooting distributed systems and using Mondemand to track down issues with various services in a distributed system.
Dave McCrory discusses what it takes to build an Enterprise Platform as a Service, covering data services, design principles, CI, monitoring, coding standards, dependencies, security, and deployment.
Camille Fournier explains what projects ZooKeeper is useful for, the common challenges running it as a service and advice to consider when architecting a system using it.
Mike Amundsen reviews patterns in developer practices and trends in services and libraries that emphasize the idea that in the end "Clients Matter, Services Don't".
In this solutions track talk, sponsored by Intel, Peter Logan looks at the evolution of the service layer in the context of API management and describes new architectural approaches for enterprise.
Anil Madhavapeddy suggests a different approach to building Internet services avoiding the complexity of today's services which incorporate many policies and security mechanisms.
Mike Krieger discusses Instagram's best and worst infrastructure decisions, building and deploying scalable and extensible services.