Book Image

AWS for Solutions Architects

By : Alberto Artasanchez
3 (1)
Book Image

AWS for Solutions Architects

3 (1)
By: Alberto Artasanchez

Overview of this book

One of the most popular cloud platforms in the world, Amazon Web Services (AWS) offers hundreds of services with thousands of features to help you build scalable cloud solutions; however, it can be overwhelming to navigate the vast number of services and decide which ones best suit your requirements. Whether you are an application architect, enterprise architect, developer, or operations engineer, this book will take you through AWS architectural patterns and guide you in selecting the most appropriate services for your projects. AWS for Solutions Architects is a comprehensive guide that covers the essential concepts that you need to know for designing well-architected AWS solutions that solve the challenges organizations face daily. You'll get to grips with AWS architectural principles and patterns by implementing best practices and recommended techniques for real-world use cases. The book will show you how to enhance operational efficiency, security, reliability, performance, and cost-effectiveness using real-world examples. By the end of this AWS book, you'll have gained a clear understanding of how to design AWS architectures using the most appropriate services to meet your organization's technological and business requirements.
Table of Contents (20 chapters)
1
Section 1: Exploring AWS
4
Section 2: AWS Service Offerings and Use Cases
11
Section 3: Applying Architectural Patterns and Reference Architectures
17
Section 4: Hands-On Labs

Summary

In this chapter, we explored what microservice architecture is exactly. We also analyzed a popular implementation of microservice architecture – EDA. We drilled down further into two kinds of EDAs, namely, the event streaming model and the publish and subscribe model.

We detailed the benefits of EDA as well as the disadvantages of using it. One more topic we covered was another common microservice architecture, called the microkernel architecture.

Lastly, we went through recommended best practices in the development of microservices. Hopefully, you can leverage the list of tried and true best practices in your next project and benefit from them.

Using architectures such as EDAs in the modern-day enterprise is no longer an option. If you continue to use legacy patterns, it is a surefire way for your project and your company to fall behind the times and lag behind your competition.

Using a microservice architecture will tend to make your application more scalable...