Rubix - Serverless architecture
Download as PPTX, PDF0 likes427 views
Serverless architecture abstracts servers away from developers by handling each request or message in its own runtime. It has evolved from monolithic runtimes shared by multiple applications to containerization with each service in its own runtime to serverless computing. Serverless scales automatically and is well suited for building APIs, event-driven apps, and stateless short tasks. Popular serverless platforms include AWS Lambda, Google Functions, and Azure Functions, which support languages like Node.js, Java, Python and C#. Challenges include lack of state and execution time limits, while advantages are infinite scalability and reduced operational complexity.
Rubix - Serverless architecture
- 1. Serverless Architecture Pim Gaemers & Jan van Zoggel 7-12-2016
- 2. Definitions BaaS (Backend-as-a-Service) vs FaaS (Function-as-a-Service) "Abstracting the server away from the developer. Not removing the server itself"
- 4. Evolution of runtimes • Monolithic runtime • Multiple applications/services share a single runtime • Containerization • A single application/service runs in its own runtime (container) • Serverless • Every request/message is handled in its own runtime
- 5. Scalability
- 7. Example architectures - Message Driven
- 8. Use cases • Implementing services/API's • Implementing event driven applications • Log analysis functions • … (stateless short running transactions)
- 9. Technical platforms Amazon Lambda https://aws.amazon.com/lambda Google Functions https://cloud.google.com/functions Microsoft Azure Functions https://azure.microsoft.com/services/fu nctions Oracle Functions (slides Thomas Kurian @ OOW 2016)
- 10. Amazon AWS Lambda • First commercial offering for FaaS / serverless • Tightly integrated in the AWS Cloud Offering • Amazon API Gateway • API Gateway can forward requests to AWS Lambda applications • Faas triggers include • Amazon DynamoDB table updates • Object modifications in AWS Buckets • Amazon Kinesis stream • Amazon IoT events • Billing is for uptime – pay per use • Billing is metered in increments of 100 milliseconds
- 11. Amazon AWS Lambda Currently the following technologies are supported: • NodeJS • Java • Python • C# (new)
- 12. Google functions • Triggers include • HTTP triggers • Cloud pub/sub triggers* • Cloud storage triggers** • Direct triggers Currently the following technologies are supported: • NodeJS *Google Cloud Pub/Sub is a fully-managed real-time messaging service that allows you to send and receive messages between independent applications. **Cloud Functions can respond to Object Change Notifications emerging from Google Cloud Storage. These change notifications are triggered in response to object addition (create), update (modify), or deletion.
- 13. Azure functions • Triggers include • Timer based triggers • Azure service triggers (record inserted in Azure db) • Microsoft SaaS triggers (e.g. file is uploaded to one Drive) • HTTP triggers • Streaming triggers • Cortana/chat bot triggers • Currently the following technologies are supported: • NodeJS • C# • F# • Python • PHP
- 14. Challenges and advantages • Challenges • No form of state (Session, object, etc.) can be stored/used in the function. This includes in memory state! • Execution time is restricted, AWS Lambda restricts execution time to 5 minutes. • Startup latency • Advantages • "Infinite" scalability • Easier operational management • Greener computing • Reduced packaging/deployment complexity
- 15. Demo