Search icon
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
AWS for Solutions Architects - Second Edition

You're reading from  AWS for Solutions Architects - Second Edition

Product type Book
Published in Apr 2023
Publisher Packt
ISBN-13 9781803238951
Pages 692 pages
Edition 2nd Edition
Languages
Authors (4):
Saurabh Shrivastava Saurabh Shrivastava
Profile icon Saurabh Shrivastava
Neelanjali Srivastav Neelanjali Srivastav
Profile icon Neelanjali Srivastav
Alberto Artasanchez Alberto Artasanchez
Profile icon Alberto Artasanchez
Imtiaz Sayed Imtiaz Sayed
Profile icon Imtiaz Sayed
View More author details

Table of Contents (19) Chapters

Preface 1. Understanding AWS Principles and Key Characteristics 2. Understanding the AWS Well-Architected Framework and Getting Certified 3. Leveraging the Cloud for Digital Transformation 4. Networking in AWS 5. Storage in AWS – Choosing the Right Tool for the Job 6. Harnessing the Power of Cloud Computing 7. Selecting the Right Database Service 8. Best Practices for Application Security, Identity, and Compliance 9. Driving Efficiency with CloudOps 10. Big Data and Streaming Data Processing in AWS 11. Data Warehouses, Data Queries, and Visualization in AWS 12. Machine Learning, IoT, and Blockchain in AWS 13. Containers in AWS 14. Microservice Architectures in AWS 15. Data Lake Patterns – Integrating Your Data across the Enterprise 16. Hands-On Guide to Building an App in AWS 17. Other Books You May Enjoy
18. Index

Containers versus VMs

There is a definite line of distinction between VMs and containers. Containers allow you to isolate applications within an OS environment. VMs allow you to isolate what appears to the users and represent it as a completely different machine to the user, even with its own OS.

The following diagram illustrates the difference:

A picture containing graphical user interface  Description automatically generated

Figure 13.1: VMs versus containers

As we can see in Figure 13.1, in the case of VM architecture, each virtual slice has its own OS and all the slices sit on top of the hypervisor. In the case of container architecture, there is only one OS installed for all the instances. There is only one container engine, but multiple binaries and applications can be installed for each slice.

Containers share a kernel at the OS level; all components are built into the OS kernel, which makes containers fast to start and, when compared to VMs, they generally have lower overhead.

VMs have a more defined isolation boundary...

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 $15.99/month. Cancel anytime}