Larry Peterson - Edge Cloud Operations: A Systems Approach
Here you can read online Larry Peterson - Edge Cloud Operations: A Systems Approach full text of the book (entire story) in english for free. Download pdf and epub, get meaning, cover and reviews about this ebook. year: 2022, publisher: Systems Approach, genre: Romance novel. Description of the work, (preface) as well as reviews are available. Best literature library LitArk.com created for fans of good reading and offers a wide selection of genres:
Romance novel
Science fiction
Adventure
Detective
Science
History
Home and family
Prose
Art
Politics
Computer
Non-fiction
Religion
Business
Children
Humor
Choose a favorite category and find really read worthwhile books. Enjoy immersion in the world of imagination, feel the emotions of the characters or learn something new for yourself, make an fascinating discovery.
- Book:Edge Cloud Operations: A Systems Approach
- Author:
- Publisher:Systems Approach
- Genre:
- Year:2022
- Rating:3 / 5
- Favourites:Add to favourites
- Your mark:
Edge Cloud Operations: A Systems Approach: summary, description and annotation
We offer to read an annotation, description, summary or preface (depends on what the author of the book "Edge Cloud Operations: A Systems Approach" wrote himself). If you haven't found the necessary information about the book — write in the comments, we will try to find it.
The cloud is ubiquitous. Everyone uses the cloud to either access or deliver services, and now it is becoming ubiquitous in
another way. As applications are disaggregated, the cloud is expanding from hundreds of datacenters to tens of thousands of enterprises. This means it is becoming increasingly important to understand the principles of cloud operations: how resources are provisioned, how service lifecycles are managed, how runtime parameters are controlled, and how system behavior is monitored and corrected over time. This book gives a comprehensive and from-first-principles description of edge cloud operations. Features include:
another way. As applications are disaggregated, the cloud is expanding from hundreds of datacenters to tens of thousands of enterprises. This means it is becoming increasingly important to understand the principles of cloud operations: how resources are provisioned, how service lifecycles are managed, how runtime parameters are controlled, and how system behavior is monitored and corrected over time. This book gives a comprehensive and from-first-principles description of edge cloud operations. Features include:
- Describes a complete edge cloud operations stack, illustrated with example open source software.
- Emphasizes underlying concepts, abstractions, design rationale, and engineering tradeoffs.
- Explains how best practices in scalable cloud services are applied to operational challenges.
- Describes the interfaces that operators and developers use to realize DevOps practices.
- Defines terminology across management domains: Telco operators, Enterprise Admins, Cloud providers
- Includes an end-to-end management platform for an operational, multi-site hybrid cloud (available on GitHub).
Larry Peterson: author's other books
Who wrote Edge Cloud Operations: A Systems Approach? Find out the surname, the name of the author of the book and a list of all author's works by series.
Larry Peterson
Manoj Hirway
Nayan B. Ruparelia
Ivo Jansch
Edge Cloud Operations: A Systems Approach — read online for free the complete book (whole text) full work
Below is the text of the book, divided by pages. System saving the place of the last page read, allows you to conveniently read the book "Edge Cloud Operations: A Systems Approach" online for free, without having to search again every time where you left off. Put a bookmark, and you can go to the page where you finished reading at any time.
Light
Font size:
↓
↑
Reset
Interval:
↓
↑
Bookmark:
Make
Edge Cloud Operations: A Systems Approach
Peterson, Baker, Bavier, Williams and Davie
Table of Contents
Foreword
Preface
Intended Audience
Guided Tour of Open Source
Acknowledgements
Chapter 1: Introduction
1.1 Terminology
1.2 Disaggregation
1.3 Cloud Technology
1.4 Future of the Sysadmin
Chapter 2: Architecture
2.1 Edge Cloud
2.2 Hybrid Cloud
2.3 Stakeholders
2.4 Control and Management
2.5 DevOps
Chapter 3: Resource Provisioning
3.1 Physical Infrastructure
3.2 Infrastructure-as-Code
3.3 Platform Definition
Chapter 4: Lifecycle Management
4.1 Design Overview
4.2 Testing Strategy
4.3 Continuous Integration
4.4 Continuous Deployment
4.5 Versioning Strategy
4.6 Managing Secrets
4.7 What about GitOps?
Chapter 5: Runtime Control
5.1 Design Overview
5.2 Implementation Details
5.3 Modeling Connectivity Service
5.4 Revisiting GitOps
Chapter 6: Monitoring and Telemetry
6.1 Metrics and Alerts
6.2 Logging
6.3 Distributed Tracing
6.4 Integrated Dashboards
6.5 Observability
About The Book
Read the Book
Build the Book
Contribute to the Book
About The Authors
Read The Latest!
Foreword
First the applications all moved to the cloud. And now theyre being torn apart. Let me explain what I mean by that.
As markets grow, the unit of function around which one can build a business shrinks. A classic example of this can be seen in the history of the automotive industry. The Ford River Rouge Complex was built in the late 1920s. At the time, mass-produced cars were relatively new, and the market was relatively small. And so factories like the River Rouge Complex had to build all the subcomponents too. Roughly, in one side of the factory went water, rubber, and iron ore, and out the other side came full automobiles. Of course, as the market for cars grew, so did a massive ecosystem of suppliers of car components: wheels, seats, floor mats, and the like. Today the large car companies are more akin to integrators than auto parts makers.
The same dynamic is happening with the application. In the 1970s the same manufacturer would build the chips, the circuit boards, the system form factor, the operating system, and each of the applications. Over time as the market has grown, the system has disaggregated. The hardware and software separated and spawned multiple independent companies. And then companies started to be built around independent applications.
The market hasnt stopped growing and over the last few years weve seen the application itself disaggregate. Commonly used subcomponents of applications are being pulled out, and entire companies and projects are being built around them. Today, if youre building an application, there are third-party APIs available for authenticating users, sending texts or email, streaming videos, authorizing access to resources, and many other useful functions.
So what does this have to do with the book youre about to read? While the last decade was a consolidation of applications into the cloud, the next decade is largely going to be about the explosion of applications and application components away from it. Now that subcomponents of workloads have been largely decoupled from having to sit with the application, they can be run anywhere. And in particular they can be run on infrastructure thats purposely built and optimized for them! In fact, we are starting to see what can only be described as an anti-cloud trend where large companies are choosing to pull some workloads back from large clouds to their own optimized infrastructure. And were even seeing startups choosing to build their own infrastructure from the get-go because they understand the cost and performance advantages of doing so.
In Edge Cloud Operations: A Systems Approach the authors provide a detailed overview of not just cloud operations (which are so last decade) but operations in this new era of distributed clouds. In many ways, the cloud era was a low point of systems, because so much below the application layer was buried deep within the engineering organizations of the three large cloud providers. But thats changing, and to change with it, you need to understand how it all works. And thats exactly why you need to read this book.
Martin Casado
General Partner, a16z
Preface
The cloud is ubiquitous. Everyone uses the cloud to either access or deliver services, but not everyone will build and operate a cloud. So why should anyone care about how to turn a pile of servers and switches into a 24/7 service delivery platform? Thats what Google, Microsoft, Amazon and the other cloud providers do for us, and they do a perfectly good job of it.
The answer, we believe, is that the cloud is becoming ubiquitous in another way, as distributed applications increasing run not just in large, central datacenters but at the edge. As applications are disaggregated, the cloud is expanding from hundreds of datacenters to tens of thousands of enterprises. And while it is clear that the commodity cloud providers are eager to manage those edge clouds as a logical extension of their datacenters, they do not have a monopoly on the know-how for making that happen.
This book lays out a roadmap that a small team of engineers followed over the course of a year to stand up and operationalize an edge cloud and then operate it 24/7. This edge cloud spans a dozen enterprises, and hosts a non-trivial cloud native service5G connectivity in our case, but thats just an example. The team was able to do this by leveraging 20+ open source components, but selecting those components is just a start. There were dozens of technical decisions to make along the way, and a few thousand lines of configuration code to write. We believe this is a repeatable exercise, which we report in this book. The code for those configuration files is open source, for those who want to pursue the topic in more detail.
What do we mean by an edge cloud? Were drawing a distinction between clouds run by the hyperscale cloud providers in their massive data centers, which we think of as the core, and those run by enterprises (or managed for them) at the edge. The edge is where the real, physical world meets the cloud. For example, it is the place where data from sensors is likely to be gathered and processed, and where services that need to be close to the end user for reasons of latency or bandwidth are delivered.
Our roadmap may not be the right one for all circumstances, but it does shine a light on the fundamental challenges and trade-offs involved in operationalizing a cloud. As we can attest based on our experience, its a complicated design space with an overabundance of terminology and storylines to untangle.
Intended Audience
We hope this book makes valuable reading for anyone who is trying to stand up and operationalize their own edge cloud infrastructure, but we also aim to provide useful information for at least two other broad groups.
First, there will be a set of readers who need to evaluate the options available, particularly to decide between using the cloud services offered by one of the hyperscalers or building their own edge cloud (or some combination of these). We hope to demystify the landscape of edge clouds for this audience to help inform those decisions.
Light
Font size:
↓
↑
Reset
Interval:
↓
↑
Bookmark:
Make
Similar books «Edge Cloud Operations: A Systems Approach»
Look at similar books to Edge Cloud Operations: A Systems Approach. We have selected literature similar in name and meaning in the hope of providing readers with more options to find new, interesting, not yet read works.
Manoj Hirway
Nayan B. Ruparelia
Ivo Jansch
Reviews about «Edge Cloud Operations: A Systems Approach»
Discussion, reviews of the book Edge Cloud Operations: A Systems Approach and just readers' own opinions. Leave your comments, write what you think about the work, its meaning or the main characters. Specify what exactly you liked and what you didn't like, and why you think so.