Hi Chris, tell us who you are and what lead you into microservices?
Working on microservices has been a natural progression as the industry has evolved. My background is working on programming languages and their associated frameworks, and part of that is ensuring that applications built using those languages and frameworks evolve to not just both support new deployment approaches, but fully exploit the new environments.
What will you be talking about at Voxxed Days Microservices?
I’ll be talking about FaaS and Serverless based applications, and about some of the recent advances in deploying serverless applications on a standard Kubernetes basis using Knative Serving.
Knative Serving makes it possible to take any microservice and deploy it in as a “serverless” application which scales on request and down to zero on idle. This in turn makes it possible to build Function-as-a-Service capabilities by creating “functions” that use standard framework APIs, build those into a microservice, and deploy them as serverless applications.
I’ll be showing how to do this, building functions using JAX-RS APIs and deploying them as serverless applications on Kubernetes.
So if we can develop a Function-as-a-service with JAX-RS, what is the difference between a FaaS and a Microservices ?
Function-as-a-Service (FaaS) really provides the combination of two concepts: developing using small “function” units of code, and running those in a “serverless” fashion so that the platform is responsible for deploying them and scaling them on demand.
If you separate these concepts, you can have the simplicity of developing using small “function” units of code using JAX-RS, and use those to build full microservices. You can then decide whether to run those microservices in a serverless fashion: essentially providing your own JAX-RS based FaaS, or run those as traditional microservices with a configured number of replicas.
Good, see you soon then
#serverless #knative #functions
My contact information