Hugh McKee is a developer advocate at Lightbend. He has had a long career building applications that evolved slowly, inefficiently utilized their infrastructure, and were brittle and prone to failure. Hugh has learned from his past mistakes, battle scars, and a few wins. And the learning never stops. Now his focus is helping developers and architects harness the power of the cloud. Hugh frequently speaks at conferences around the world. He is the author of Designing Reactive Systems: The Role Of Actors In Distributed Architecture.
For developers, one of the most exciting things about serverless is FaaS — Functions as a Service. FaaS platforms allow developers to focus most of their attention on writing code and much less time on the other stuff.
Traditionally, in the pre-serverless universe, the ‘other stuff’ consists of setting up the environment needed to run our code — the runtime VMs or K8 pods, networks, databases, schemas, URLs, passwords, environment settings, serialization, and more.
When you think about it, the ratio of ‘other stuff’ to pure heads down in the zone development is often 80/20. We spend most of our time not doing what we love as developers — writing code — because it takes so much time and effort to get everything set up to run our code.
Ok, with serverless, we can develop these cool new FaaS, but what kind of functions can we implement? In this session, we will look at how you can implement back-end app components, such as key-value, event-sourcing, CQRS, pub/sub, and more, all in an as-a-service way with Java and Akka Serverless. Also, let’s see how doing things as a service flips the ‘other stuff’/’fun stuff’ ratio from 80/20 to 20/80 or better.