Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
AWS for Solutions Architects

You're reading from   AWS for Solutions Architects Design your cloud infrastructure by implementing DevOps, containers, and Amazon Web Services

Arrow left icon
Product type Paperback
Published in Feb 2021
Publisher Packt
ISBN-13 9781789539233
Length 454 pages
Edition 1st Edition
Tools
Arrow right icon
Toc

Table of Contents (20) Chapters Close

Preface 1. Section 1: Exploring AWS
2. Chapter 1: Understanding AWS Cloud Principles and Key Characteristics FREE CHAPTER 3. Chapter 2: Leveraging the Cloud for Digital Transformation 4. Section 2: AWS Service Offerings and Use Cases
5. Chapter 3: Storage in AWS – Choosing the Right Tool for the Job 6. Chapter 4: Harnessing the Power of Cloud Computing 7. Chapter 5: Selecting the Right Database Service 8. Chapter 6: Amazon Athena – Combining the Simplicity of Files with the Power of SQL 9. Chapter 7: AWS Glue – Extracting, Transforming, and Loading Data the Simple Way 10. Chapter 8: Best Practices for Application Security, Identity, and Compliance 11. Section 3: Applying Architectural Patterns and Reference Architectures
12. Chapter 9: Serverless and Container Patterns 13. Chapter 10: Microservice and Event-Driven Architectures 14. Chapter 11: Domain-Driven Design 15. Chapter 12: Data Lake Patterns – Integrating Your Data across the Enterprise 16. Chapter 13: Availability, Reliability, and Scalability Patterns 17. Section 4: Hands-On Labs
18. Chapter 14: Hands-On Lab and Use Case 19. Other Books You May Enjoy

Choosing the right tool for the job

In the previous sections, we learned how to classify databases, and we learned about the different services that AWS provides. Now comes the hard part: deciding which service is the right one for our particular use case. As technologists, we often fall in love with the latest shiny new object we have learned about, and because we have a hammer, everything looks like a nail. Firstly, we should spend a significant amount of time clearly articulating the business problem we are trying to solve. Often, your client will have a set of requirements and, based on your experience, you know they want or need something else. The problem statement should be carved and shaped to its most precise and simple level. Once you get signoff or agreement from all parties involved, only then is it time to start thinking about what the right tool for the job is.

Some of the questions the requirements should answer are as follows:

  • How many users are expected...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at AU $24.99/month. Cancel anytime