The document discusses GitOps and a new paradigm called cloud native applications. It promotes GitOps as an approach where the entire system, including code, config, monitoring rules and policies are described in a Git repository. This allows the entire system to be destroyed and re-built with no human intervention. It then describes Automium, a solution the author's company built based on GitOps fundamentals to help with cloud transformations.
4. Enter Cloud Suite
The first European,
multi-region, open source
cloud IaaS
AMS
MIL
FRA
5. Twenty years’ experience
in datacenter and cloud services
led us to believe that stability,
reliability and performance
are not in the product, but
in the process.
6. Conway’s Law
Organizations which design
systems […] are constrained
to produce designs which are
copies of the communication
structures of these organizations.
7. Siloed functional teams… … lead to siloed application architectures.
UI specialists
Middleware specialists
DBAs
8. If you can’t feed a team
with two pizzas,
it’s too large.
Jeff Bezos
“
12. A microservices architecture
is distributed
A monolithic application
puts all its functionality
into a single process…
…and scales by
replicating the monolith
on multiple servers
…and scales by
distributing these
services across servers,
replicating as needed.
A microservices
architecture puts each
element of functionality
into a separate service…
15. “Cloud Native applications are a combination of existing
and new software development patterns.
The existing patterns are software automation
(infrastructure and systems), API integrations,
and services oriented architectures.
The new cloud native pattern consists of microservices
architecture, containerized services,
and distributed management and orchestration.
CNCF (Cloud Native Computing Foundation)
16. There’s no benefit in moving
your monolithic app to the
cloud as it is (“lift and shift”)