book

Cloud Native Patterns

by Cornelia Davis

May 2019

Intermediate to advanced

400 pages

14h 2m

English

Manning Publications

Read now

Unlock full access

1.1. Today’s application requirements1.2. Introducing cloud-native software1.3. Cloud-native and world peaceSummary
2.1. The obstacles2.2. The enablersSummary
3.1. The cloud(-native) platform evolution3.2. Core tenets of the cloud-native platform3.3. Who does what?3.4. More cloud-native platform capabilitiesSummary
4.1. We’re (usually) taught imperative programming4.2. Reintroducing event-driven computing4.3. My global cookbook4.4. Introducing Command Query Responsibility Segregation4.5. Different styles, similar challengesSummary
5.1. Cloud-native apps have many instances deployed5.2. Stateful apps in the cloud5.3. HTTP sessions and sticky sessions5.4. Stateful services and stateless appsSummary
6.1. Why are we even talking about config?6.2. The app’s configuration layer6.3. Injecting system/environment values6.4. Injecting application configurationSummary
7.1. Having empathy for operations7.2. Single-app lifecycle, multiple-instance lifecycles7.3. Coordinating across different app lifecycles7.4. Let’s see this in action: Credential rotation and app lifecycle7.5. Dealing with ephemeral runtime environments7.6. Visibility of app lifecycle state7.7. ServerlessSummary
8.1. The service abstraction8.2. Dynamic routing8.3. Service discoverySummary
9.1. Request retries9.2. Fallback logic9.3. Control loopsSummary
10.1. Circuit breakers10.2. API gateways10.3. The service meshSummary
11.1. Application logging11.2. Application metrics11.3. Distributed tracingSummary
12.1. Every microservice needs a cache12.2. Moving from request/response to event driven12.3. The event log12.4. Event sourcing12.5. We’re just scratching the surfaceSummary

Content preview from Cloud Native Patterns

Acknowledgments

My cloud-native journey began in earnest in 2012 when my boss at the time, Tom Maguire, asked me to start looking into this PaaS (Platform as a Service) thing. As a member of the Architecture group in the EMC CTO office, looking at emerging technology was not new for us—but boy, did this one pan out! I will forever be grateful to Tom for the impetus and for giving me the space to explore.

By early 2013, I had learned enough to know that this was the space for me to work in for the foreseeable future, and with the creation of Pivotal Software, I had a place to do that work. I have Elisabeth Hendrickson to thank, first for welcoming me to the Cloud Foundry party—even while I was still at EMC—and for introducing me to James Watters. ...