Cloud Application Architecture Patterns

Chapter 7. Cloud-Native Storage

For cloud-native applications to work better in the cloud, they need to persist their data in storage that works better in the cloud.

A Cloud-Native Application (Chapter 3) can pose a difficult problem: you would like for one to be a Stateless Application, and yet most applications have state. If the application’s state isn’t in the application, where does the state go? Microservices Architecture (Chapter 4) seems to compound this problem because each Microservice has its own Self-Managed Data Store. So the question is not just what one application does with its one set of data but what all of its Microservices do with all of their separate sets of data.

The cloud has brought developers and architects a wealth of new options for data storage. Long gone are the days when the only data storage option was an enterprise relational database for all applications, regardless of whether the type of data that was being stored was suited for a table-based representation. However, with new choices come new potential problems. In particular, the nonfunctional requirements that an enterprise relational database addresses now become more important, as the number of ways in which these requirements can be addressed increases.

Introduction to Cloud-Native Storage

This chapter explains how to store data in ways that work better on the cloud and that enable applications to use the data more easily. While the cloud includes storage infrastructure, databases hosted ...