Cloud Foundry Summit Asia 2015

In this workshop we'll look at how to build cloud-native Java
applications. A cloud native application is one that is designed to
fully exploit a cloud platform both in the application layer - where
things decompose into microservices - and at the data layer where
NoSQL offers better horizontal scaling and fitness for specific
purpose.

We'll look at:
- writing services and handling non-functional requirements like
metrics and logging with Spring Boot
- scaling out safely and building fault-tolerant systems using Spring
Cloud and its support for distributed systems patterns like the
circuit breaker, service registration and discovery, messaging, and centralized
configuration management.
- offloading as much operational work as possible to the platform, Cloud Foundry, so that it wears the pager when a microservice falls over

This year (2015) has seen a series of key architectural changes to CF services. Mainly adding the ability for all service operations to be done asynchronously, adding arbitrary parameters to all service operations, and finally, externalizing credentials so that service keys can be created from a service without having to bind the service to an app. While seemingly a set of simple changes, in actuality these changes really result in "CF Services 3.0" where the space for user stories around all CF services that are supporting these features has just increase significantly. In this talk we will brush up on the technical details for these three CF services changes and give a laundry list of use cases that are made possible by these additions.

Cloud Foundry provides consistent user experience across cloud providers, this talk introduces the fundamentals and best practices on how a customer should be preparing onboarding to a new cloud provider, utilizing template to prepare the cloud environment, configuring the service brokers to manage services, etc.  We will also share the background on how a cloud provider interacts with Cloud Foundry platform. Using Azure as example, we will introduce the long term roadmap for Cloud Foundry on Azure.

Lattice is a slimmer, meaner, fitter version of Cloud Foundry. This talk will cover how you can use Lattice, what’s missing from the full-fat Cloud Foundry, and how Lattice helps to explore the Cloud Foundry application lifecycle. We’ll also be looking at how Lattice helps with Cloud Foundry core development and provides a showcase of the latest Cloud Foundry components.

I propose to lead a simple presentation (the explanation part of a workshop) to help non-developers and beginner developers "Deploy Your First Cloud Foundry App". In the workshop, I will show how to deploy an app on a Cloud Foundry Service Provider. I will give the attendees the choice of Pivotal Web Services or IBM Bluemix. After deploying the web app, I will show the attendees how to add a database to their web app. We will end with a demonstration suggestions for different programming languages like Express for Node.js, Spring Boot for Java, etc.

UAA, as a core component of Cloud Foundry, is responsible for authenticating and authorizing requests between platform users (e.g. those that push apps) and platform components (e.g. the cloud controller). But when it came to doing auth for the apps you push and the end users of those apps, using the built-in UAA wasn't the best fit, and you could easily end up shooting yourself in the foot. Until now. This talk will guide you though UAA's new multi-tenancy features, and show you how to use the built-in UAA to create arbitrary authorization scenarios for your products without the danger of affecting the security of the core platform. With this level of freedom, you'll have complete and fine-grained control over who is allowed to access your product's components, and how those components are allowed to interact with one another.