Wednesday 11th September, 2013
12:45pm to 2:15pm
It’d be nice to assume everything remains the same from one environment to another, but the realties of today’s deployment targets (clouds, app servers, etc.) make this difficult. An application may target one in-memory database in development and target a traditional database in production. A/B testing is a common practice that lets you incrementally expose potentially high risk features. Feature switches can be invaluable; should something go wrong, you can revert to a known state. All of these use cases, and more, can be handled using the Spring framework. Join JavaOne Rock Star and Java Champion Kevin Nilson and Spring Developer Advocate Josh Long for a look at how you can run your application in differing environments using the Spring framework.
Presentation Summary - Overview of related Spring 3.2 features - Detailed Look at Spring Profiles - Examine use cases for using Profiles to support Multi Environments - Present how just.Me is using spring profiles within AWS (just.me is a startup in Google's Startup Labs where Kevin is VP of Engineering) - Show live examples of switching profiles during runtime.
Objective 1 Introduce Spring 3.2 profiles Objective 2 Show how to target one environment for development and another environment for production Objective 3 Show live examples of reloading profiles at runtime
Sign in to add slides, notes or videos to this session