Micro Service Design Patterns

 Now let's have a look at a full microservices architecture pattern. So let's look at a design pattern that fully utilizes microservices. Now the microservice architecture pattern is not bound by that typical three-tier architecture which we've examined so far. However, that's a popular pattern, and it can realize significant benefits when used with serverless resources. So in our architecture this time, each of the application components are completely decoupled and independently deployed and operated. Amazon API Gateway manages their API, and the functions subsequently are executed by AWS Lambda, and that's all you need to build the microservice. That means your team is free to do other things. 

The challenge with microservice environments is that it does create a few difficulties, like there's repeated overhead for creating each traditional server-designed microservice. We've got to optimize the servers, the density, utilization, et cetera. So when we create microservices using serverless resources, those problems become simpler and easier to solve. The serverless microservice pattern lowers that bar to creation of each subsequent microservice. And optimizing server utilization is not so much of an issue with this pattern. An API gateway provides programmatic-generated client SDKs, which can make it even easier to integrate with other services and other runtimes. Okay, so there's a lot more detail we could go into on both microservice design and serverless design. You don't need to know a lot of granularity for the Solution Architect Associate exam, okay? But this is a very interesting topic. So by all means, once you've passed the exam, come back and learn more about these brilliant architectures.