You're reading from AWS for Solutions Architects The definitive guide to AWS Solutions Architecture for migrating to, building, scaling, and succeeding in the cloud

Product type Paperback

Published in Apr 2023

Publisher Packt

ISBN-13 9781803238951

Length 692 pages

Edition 2nd Edition

Tools

AWS

Concepts

Cloud Computing

Authors (4):

Neelanjali Srivastav

Saurabh Shrivastava

Alberto Artasanchez

Imtiaz Sayed

View More author details

Table of Contents (19) Chapters

AWS for Solutions Architects, Second Edition: Design your cloud infrastructure by implementing DevOps, containers, and Amazon Web Services

1 Understanding AWS Principles and Key Characteristics FREE CHAPTER

2 Understanding 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 Dive efficiency with Cloud Operation Automation and DevOps in AWS

10 Bigdata and streaming data processing in AWS

11 Datawarehouse, Data Query and Visualization in AWS

12 Machine Learning, IoT, and Blockchain in AWS

13 Containers in AWS

14 Microservice and Event-Driven Architectures

15 Domain-Driven Design

16 Data Lake Patterns – Integrating Your Data across the Enterprise

17 Availability, Reliability, and Scalability Patterns

18 AWS Hands-On Lab and Use Case

Database consistency model

Transaction data consistency in the context of databases refers to the requirement that any database transaction can change data only in allowed ways. Data written to the database will be validated against a set of rules and constraints, and all these checks must always be passed before the data is made available to other users. Currently, there are two popular data consistency models. We'll discuss these models in the following subsections.

ACID data consistency model

When database sizes were measured in megabytes, we could have stringent requirements that enforced strict consistency. Since storage has become exponentially cheaper, databases can be much bigger, often measured in terabytes and even petabytes. For this reason, making databases ACID-compliant for storage reasons is much less prevalent. The ACID model guarantees the following: