Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
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

Learning about frontend user interfaces

Now that we have analyzed the languages that we can use for our microservice and we understand the environments that we can use to deploy our service, let's delve further into the architecture.

Let's start by looking at a critical component of the architecture—the frontend user interface. It is possible to create a microservice that does not have a frontend. The reason to do this would be if our application is not meant to be used by humans—in other words, all our service clients are other computing services. However, many microservices will need some form of frontend, even if it's only for some parts of the service.

Since smartphones and tablets took hold some time ago (let's say in 2007, with the release of the iPhone), it is no longer enough to create your frontend so that it focuses on desktop development. There are all kinds of form factors that need to be considered—from a small phone to...

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 $19.99/month. Cancel anytime
Banner background image