From the course: Learning Cloud Computing: Serverless Computing

A good fit for serverless computing

From the course: Learning Cloud Computing: Serverless Computing

Start my 1-month free trial

A good fit for serverless computing

“

- [Instructor] The best way to explain the use of serverless computing is to walk through an example. Lets do that. So we are going to look at it a fictional company called Southern Hammocks, who produces and sells hammocks. So they have a problem, they need a new inventory application to deal with an increase in sales. So moving forward, we need to look at different platforms to build this application and get it into production. They just moved to Amazon web services, and they've migrated the data there and they are fairly happy with their new environment. They need to focus on scalability because this is something they don't want to do every few years. As there sales number increases and use of data increases, they want something that's able to keep up. And also they have to consider the fact that agility is going to be core to this. The application is going to go through lots of changes as they move into different markets and sell different products. And they want to be have the flexibility to do that pretty much is needed. So some decisions have to be made. Number one, should we leverage this technology at all? And what I recommend that we look at is reasons it's a fit and reason it's not a fit. So it's typically a fit if it's something that's Net New which our application is. This is going to be a Net New inventory system that they're building from scratch. The ability to look at something that provides scaling or auto scaling and they value that because they need something that can scale up to whatever sales or the needs that are going to be done. Something that's service oriented, the ability to leverage these API is to expose them to people outside of the organization to access some of their inventory data. Such as their suppliers or their customers. However it may not be a fit if they're moving to a legacy system such as a main frame system. So it doesn't seem to be that much value in scaling, and really there's no need for services or APIs. So keep in mind if we're doing Net New, reconsidering applications and databases, if we're looking at auto scaling, we're looking at as needed cloud services or the ability to in essence take the resources that we need as we need it. The ability to provide elasticity, a true elasticity meaning we can in essence expand up to any number of resources that we need, and then return those resources back to the pool, once they're no longer needed. And also the ability to deal with Microservices and the ability to deal with functions. And so we're in essence exposing part of our application out to the public because in some instances we want them to leverage the system, such as going through our inventory database to determine if we have something on hand that we can sell.

Contents