Baruch Sadogursky discusses creating DSLs which support plugins written both in Groovy or Java, addressing good public API design practices, security, and classpath isolation.
Mike Wiesner advises on dealing with security tradeoffs when creating Servlet Container, Spring MVC or Spring Integration type of applications.
Greg Turnquist demoes using Spring Mail, Security, REST, GridFS, Bootstrap and jQuery in a production grade Grails application.
Joe Rinehart discusses some of the essential security topics for Grails/Java Web applications, showing how Grails can make life easier and the pitfalls of attempting to secure highly dynamic code.
Watkins and Hanna discuss the top 5 security mistakes made by developers, examining them in detail by looking at the code and highlighting the risks from both the consumer and developer perspective.
Anil Madhavapeddy suggests a different approach to building Internet services avoiding the complexity of today's services which incorporate many policies and security mechanisms.
Michiel de Jong suggests solving the data privacy and scalability issues by enabling mobile apps to connect to user's preferred back-end using Dropbox.js, GDrive JS, NimbusBase, remoteStorage.io, etc.
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.
Justin Kobel introduces claims-based authentication, what are claims, their life cycle, explaining how to consume them in .NET through a number of demoes.
Burt Beckwith discusses the security risks web applications may face (XSS, CRSF, SQL injection) and the libraries and plugins that developers can use to secure their Grails applications.
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.
Neil Killick proposes ways to reduce risk and uncertainty, calculate a product’s price, determine delivery dates and roadmap, do Scrum and XP without using estimates.