Cloud Application Architecture Patterns

Chapter 7. Cloud-Native Storage

A Note for Early Release Readers

With Early Release ebooks, you get books in their earliest form—the author’s raw and unedited content as they write—so you can take advantage of these technologies long before the official release of these titles.

This will be the 7th chapter of the final book.

If you have comments about how we might improve the content and/or examples in this book, or if you notice missing material within this chapter, please reach out to the editor at [e-mail].

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 can be a bit of a contradiction: 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 seems to compound this problem because each microservice has its own Self-Managed Data Store. So the question is not just what does one application do with its one set of data, but what do 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 or not the type of data that was being stored was suited for a table-based representation. However, ...