Downloaded 35 times
More Related Content
Similar to Building a serverless app
Building a serverless app
- 1. Building a ServerlessApp Vinay Krishna
- 2. Pre-cloud days When developer’slife was easy only code was complex Really?
- 3.
- 4. Not only Development– What about Deployment • We also need to think a lot about • Servers • Budget / Cost • Deployment time • Scale • Migration • Maintenance • Connectivity • Availability
- 5. Later • As demandgrows, it became more complicated • Many servers • Providing racks, power, Internet access and other key resources. • Dealing with provisioning, clustering, and maintaining servers required spending: • Lots of money (capital expenditures, power, internet, cooling, security) • Tons of time and detailed planning (contingency, develop/test/produce, site growth, and so on)
- 6.
- 7. The shift toCloud days No worry on servers, manage infrastructure on demand
- 8.
- 9. What does itmean? • On demand service • Cost reduction • Scalability and Elasticity • Easy Maintenance • High Performance • Multi-tenancy • Reliability • Resource pooling
- 10. Cloud – Seismicshift • Provides an almost limitless supply of virtual machines • With no upfront costs • With just a bit of effort, developers can • fire up servers with their operating system of choice • load in their applications (custom or open-source) • and they’re off and running. • Launching hundreds of servers and coordinating among them is a bit more work but it’s still far easier than it was just few years ago. • Total cost of ownership of servers has fallen dramatically.
- 11.
- 12. Yet, Shift isnot over Oh really!! What’s left now?
- 13.
- 14. VMs Machine as unitof scale Abstracts the Hardware Containers Applications as the unit of scale Abstracts the OS Serverless Functions as the unit of scale Abstracts the language runtime I want to configure machines, storage, networking and my OS I want to run servers, configure applications and control scaling I want to run my code when it’s needed
- 15. Still, it needsserver • Serverless does not mean “No Server” required • It means think less about servers • such as scalability, high-availability, infrastructure-security, and so forth https://pbs.twimg.com/media/Cr1HEpnXgAAK9vV.jpg
- 16. Serverless • Run codewithout provisioning or managing servers • Backend as a Service • A model for providing web app and mobile app developers with a way to link their applications to backend cloud storage and APIs exposed by back end applications while also providing features such as user management, push notifications, and integration with social networking services. • Function as a Service • Develop, run, and manage application functionalities without the complexity of building and maintaining the infrastructure typically associated with developing and launching an app Pay only for time your code runs
- 17. Scenarios • Time basedprocessing • Event based activity / processing • Serverless web application architectures • Serverless mobile backends • Real-time stream processing • File Processing • Data and Analytics • Websites • Mobile applications
- 18. • Problem • Replicateone log from one data center to another • Analyze the logs • Take action • Before Serverless • Setup a VM/Container/WebJobs • Build/Patch/Deploy • Monitor • Manage FTP cred • Use FTP library • Use cloud service SDK • Using Serverless • Setup a VM/Container/WebJobs • Build/Patch/Deploy • Monitor • Manage FTP cred • Use FTP library • Use cloud service SDK
- 20.
- 21. Pre-requisites • Create yourAWS account • Create pair or group • Knowledge of Node.js / Python / Java
- 22. My first serverlessapplication • Write your “Hello participants!” serverless app • Test the app
- 24.
- 25. Monitor and Metrics CloudWatchand CloudTrail
- 26.
- 27.