Serverless solutions for backend development

Editor's Notes

• #2: Welcome to my lecture about serverless solutions in backend development. In the next 30m’ I am going to to expose you to a tech that I used a lot at my last job making an IOT device. After a short build up I’ll explain what is FaaS , How can it help us and what are the pros and cons for using it.
• #3: You may have started as a small computer on a desktop, You might have opened you own cloud infra’.
• #4: You Can have your servers on the cloud - use them as simple servers - but then you have to do all devops yourself - So you use kubernetes ,docker , Chef(I hope).
• #5: Google app engine or elastic beanstalk - they manage you services deployment and connections - you can automate recovery.
• #6: BaaS: Easily managed, Give you predefined abilities - Firebase: Use as you need but can be limiting. Heroku - It’s just a place to run your code - You write services and upload them - not a bad thing. - You need to wire it to anything you want from other clouds. Hoodie
• #7: Your architecture grows, You might have a monolith or a bunch of micro services , You chose the stack you feel good with.
• #8: You want connect to an event on your system, DB write, Image upload or you want to add a model written by your new Data science team. Monolith: You’ll have to make sure that you are writing in your same language and that it doesn’t crash your server Microservices: Devops are ready to deploy it and scale it, Connect it to the echo sytstem - hooks events, If it’s a new language hooking it to events needs to be re-written. I want to extend events on my firebase/ azure iot . that are not part of it. A lot of work when you just want to send this featue out and get some insights. Everyone is writing services - even data sciencetists -
• #9: You want connect to an event on your system, DB write, Image upload or you want to add a model written by your new Data science team. Monolith: You’ll have to make sure that you are writing in your same language and that it doesn’t crash your server Microservices: Devops are ready to deploy it and scale it, Connect it to the echo sytstem - hooks events, If it’s a new language hooking it to events needs to be re-written. I want to extend events on my firebase/ azure iot . that are not part of it. A lot of work when you just want to send this featue out and get some insights. Everyone is writing services - even data sciencetists - A new server for each logic?
• #10: Data scientists or developers are like...
• #12: In the last few years I worked for Communication companies, I did embedded , mobile SDK’s , Cloud architecting for an IOT device and today I am doing E Commerce - Mostly React/React native. Although different markets I found that some basic engineering issues are the same everywhere I went.
• #13: Aws lambda, Azure functions, google functions. All cloud providers have them. There are also on premise solutions.
• #14: Choose what triggers your code. Write a function on a selected env. Integrate it to other parts of the system (not by code). Provider will scale it for you - Every trigger is an isolated instance that dies in the end,
• #15: Choose what triggers your code. Write a function on a selected env. Integrate it to other parts of the system (not by code). Provider will scale it for you - Every trigger is an isolated instance that dies in the end,
• #16: Code only takes event and context: Event: What happend and accessing the data which triggered it. Context: What stage I am deployed at ENV params.
• #18: Each function’s life cycle ends when the event is done.
• #19: Each function’s life cycle ends when the event is done.
• #20: Each function’s life cycle ends when the event is done.
• #21: Each function’s life cycle ends when the event is done.
• #22: Connect FireBase to your cloud.
• #23: Twilio is a cloud communications platform as a service company based in San Francisco, California. Twilio allows software developers to programmatically make and receive phone calls and send and receive text messages using its web service APIs
• #24: Twilio is a cloud communications platform as a service company based in San Francisco, California. Twilio allows software developers to programmatically make and receive phone calls and send and receive text messages using its web service APIs
• #26: Today more than 45,000 developers have access to a growing library of 3,500+ algorithmic microservices. Our team is dedicated to reaching developers on every corner of the earth, we hope you consider joining us. They give you a simple blueprint to insert algorithms into your flow. This is another way for companie to create quick integrations to saas.
• #27: Twilio is a cloud communications platform as a service company based in San Francisco, California. Twilio allows software developers to programmatically make and receive phone calls and send and receive text messages using its web service APIs
• #28: https://trackchanges.postlight.com/serving-39-million-requests-for-370-month-or-how-we-reduced-our-hosting-costs-by-two-orders-of-edc30a9a88cd They created a tool for scraping website in a structured manner. By turning serverless they reduced complexity, Easily cached requests and reduces hosting costs. Reducing from 10K
• #29: https://trackchanges.postlight.com/serving-39-million-requests-for-370-month-or-how-we-reduced-our-hosting-costs-by-two-orders-of-edc30a9a88cd By turning serverless they reduced complexity, Easily cached requests and reduces hosting costs. Reducing from 10K