Serverless architectures refer to applications that significantly depend on “cloud” services (knows as Backend as a Service) or on custom code that’s run in ephemeral runtime (Function as a Service or “FaaS").
To application developers, “serverless” mean app where some certain logic of it is still written by the developer but unlike traditional architectures or microservices is run in stateless compute runtime that is event-triggered, may only last for one invocation, and fully managed by a cloud. Serverless helps developers to transfer responsibility for keeping their apps up and running as well as scaling out their workload capacity without involving DevOps/ops as we got used to.
In this talk we will go through whole “serverless” thing: from decomposing app and its logic to microservices and further to smaller bits, i.e. functions to defining data flow through functions and building their fault-tolerant pipeline. Moreover, we will go through a demo that highlights key takeaways:
- what are functions, what it could and could not be
- how to design scalable architecture without getting into troubles by hitting concrete bottlenecks
- how serverless can help scaling in/out compute capacity for data processing
The demo itself will include examples of applying serverless architecture pattern to emotion recognition app based on TensorFlow and OpenCV 3.3
in __on Friday 20 April at 15:15 **See schedule**