Burt Beckwith discusses performing transactions in Grails, covering services, customizing transaction attributes (isolation, propagation levels), two-phase commit, using JMS, and testing the code.
The role of API management infrastructure in API Security, API Access Control and API Federation and its interaction with enterprise infrastructure, social identity and application developers.
Ben Christensen describes Netflix API's evolution to a web service platform serving all devices and users, the challenges met in operations, deployment, performance, fault-tolerance, and innovation.
Kyle Boon reviews 3 frameworks for building RESTful WS- Grails, Dropwizard and Ratpack-, comparing their code readability, maintainability, deployment, metrics collection, scalability and testability.
Brendan Eich surveys interesting developments in the Web platform, analysing emergent trends, and making some predictions.
Nick Kolegraff discusses common problems and architecture to support all the phases of data science and how to start a data science initiative, sharing lessons from Accenture, Best Buy, and Rackspace.
Dan Woods discusses using Spring Integration and design patterns to implement a message-driven architecture in Grails to allow for better modularity, scalability, and code reusability.
Jeremy Edberg discusses how Netflix designs their systems in order to survive outages, network latency and random instance failure.
Blake Dournaee covers the often forgotten back-end architecture for mobile apps which should expose cross-platform APIs to mitigate some of the effects of mobile O/S fragmentation.
Steve Pember discusses creating Grails applications integrating message broker technologies, especially RabbitMQ, and applying SOA principles.
Paco Nathan reviews an example data analysis application written in Cascalog used for a recommender system based on City of Palo Alto Open Data.
Jeff Magnusson details some of Netflix' key services: Franklin, Sting and Lipstick.