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

Microservice examples

In the previous section, we packed a lot of information into a small space. We listed and discussed a lot of AWS services that can be used to build microservices. This might seem overwhelming, and perhaps we confused you. It is important to note that when building your own microservices, many of the services listed will not be used. Your job as an architect is to be able to discern which one is the right tool for your given business requirements. Another important consideration when choosing services is to make sure that the architecture you propose fits with the culture of the company. For example, you might not want to recommend using Java as the programming language for the microservices if the current client is a Microsoft shop—C# might be a better recommendation. Let's try to dial it down and now work on a simple microservice example using DDD.

Using microservices to transform media files

Cross-device and cross-platform support for media...