Containers, microservices, serverless: On being serverless or serverful

The first generation of microservices was primarily shaped by Netflix OSS and used by numerous Spring Cloud annotations all throughout your business logic. The next generation of microservices will use sidecars and a service mesh. In this session, we'll give you a taste of Envoy and Istio, 2 open source projects that will change the way you write distributed, cloud native, Java applications on Kubernetes.

Then we'll show you the power of Serverless architecture. Serverless is a misnomer; your future cloud native applications will consist of both microservices and functions, often wrapped as Linux containers, but in many cases where you, the developer, ignore the operational aspects of managing that infrastructure.

In this session, we start off building a Function-as-a-Service (FaaS) platform with Apache OpenWhisk deployed on OpenShift. With OpenShift being the de facto platform for cloud-native Java applications, we'll explore further to see how to make cloud-native Java applications (a.k.a microservices) complement the serverless functions.

  • Date:Tuesday, May 8
  • Time:10:30 AM - 11:15 AM
  • Room:207
  • Location:Moscone South - 207
  • Session Type:Breakout
  • Session Code:S2104
  • Best for people who:Build applications, Design application/system architectures
  • Technical difficulty:Working knowledge required
  • Primary solution:None of the above
  • Topic(s):Application delivery, Application development
  • Session Includes:Demo
  • Time slot:Morning
  • Trail maps:From the office of the CTO, Cloud-native application development
  • Links:

    Want to learn more about tools & technology strategy? Don't miss these related sessions:

Burr Sutter
Red Hat