Cloud-Native Software Architecture: An Overview and Foundations of Cloud Computing and Cloud-Native Architecture
Conditions
A brand-new, unused copy in perfect condition.
Formats
Conditions
A brand-new, unused copy in perfect condition.
Conditions
A brand-new, unused copy in perfect condition.
Formats
Conditions
A brand-new, unused copy in perfect condition.
Running an application in the cloud does not, by itself, make it cloud native, in the same way that writing a class in Java is not enough for a system to be object-oriented. The distinction is structural, not topological - and that distinction is the subject of this book.
Written for students of Computer Science and Software Engineering, and for professionals who operate systems in production, the text follows an explicit criterion: presenting microservices, containers, orchestration, and continuous delivery without returning to the Computer Science foundations that make them intelligible produces tool operators rather than engineers. Each technology is therefore introduced alongside the principle that supports it. Modularity in Parnas (1972). Process isolation in kernel primitives that precede Docker by decades. Reliability as an economic decision rather than an absolute ideal.
Eleven chapters in constructive progression: the foundations of computing (storage, networking, operating systems, databases); the foundations of cloud computing from the NIST operational definition; the four pillars of cloud-native architecture; cloud-native design patterns and the Twelve-Factor contract; DevOps and automation; infrastructure as code and GitOps; microservices; containers and Kubernetes; continuous integration and delivery; observability and reliability engineering; and Software-as-a-Service architecture, with the silo, bridge, and pool models.
A methodological caveat runs through the book. The literature on cloud native is, to a large extent, produced by the industry that sells these services. Here, commercial claims are contrasted with academic sources, open standards, and accounts of failure. The reader is encouraged to distrust absolute promises, including those that appear in this work. Two questions sustain the reading: what problem does this technology solve, and what new problems does it introduce?
There are currently no reviews. Be the first to review this work.