Cloud Native Patterns (Jamie Dobson, Container Solutions)

container-solutions.com info@container-solutions.com Patterns and Case Studies @JamieDobson
info@container-solutions.com
container-solutions.com
09.05.2019
@JamieDobson
@containersoluti
Cloud Native Patterns
What We Learnt In
The Last Five Years
London Microservices
Meetup

container-solutions.com info@container-solutions.com All Hands - End of Sprint - 08.05.2019 @JamieDobson
Agenda
■ Introduction - The Quality Without a Name
■ What is a Pattern Language?
■ What is a Cloud Native Pattern Language?
■ Cloud Native and Patterns
■ Some Examples
■ Scenarios that Create Tension
■ Patterns and the Maturity Matrix
■ Conclusion - Writing Your Own Story

Introduction
The Quality Without a Name

container-solutions.com info@container-solutions.com All Hands - End of Sprint - 08.05.2019 @JamieDobson
There is a central quality which is the root
criterion of life and spirit in a man, a
town, a building, or a wilderness. This
quality is objective and precise but it
cannot be named
ValueProposition

Praxis (from Ancient Greek: πρᾶξις, romanized:
praxis) is the process by which a theory, lesson, or
skill is enacted, embodied, or realized. "Praxis" may
also refer to the act of engaging, applying, exercising,
realizing, or practicing ideas.

What is a Pattern Language?
A Collection of Design Decisions

container-solutions.com info@container-solutions.com Hermes - The CS Strategic Execution Method @JamieDobson
A pattern language is like a dictionary. a pattern
language collects design decisions about a particular
problem domain.
Look up a pattern and you will find a summary of the
problem (words), links to related problems (other words),
the proper use of the pattern (grammar) and how it
can be used (syntax).

What is a Cloud Native Pattern
Language?
A Collection of Design Decisions of Cloud Native

Our cloud native pattern language is a collection of
design decisions and the context in which they work.
best practice is, by definition, yesterday’s practice.
We prefer to think of the patterns as emerging
practices.

Our pattern language will grow over time as will the way in
which the patterns can be reconfigured to create designs
we have thus far not even considered.

The Cloud Native QWAN
Knowing it When You See It

Cloud Native QWAN
● Microservices are used to build a whole application from a collection of smaller services, each handling a different function or
utility and then harnessed together. This modularity makes the application faster and easier to develop, test and release.
“Decomposing” an application into a modular set of services also makes it simpler to understand.
● Containerisation encapsulates an entire application into a single package, including its operating system and all dependencies
(like the different libraries and configuration files needed to run it). A containerised application is entirely self-contained, secure,
and transportable, moving easily from developer’s desktop to test environment and on into production.
● Cloud services, or Infrastructure-as-a-Service, take the components traditionally present in on-premises data centers, such
as servers, data storage and networking hardware, and instead provide them via the internet. So how do you know Cloud
Native when you see it? The core of Cloud Native is how we create and deliver software, not where.

Example Patterns
The Business Case and Microservices

Structure
Deﬁnition
In This Context:
Therefore:
Consequently:
Related Patterns:

Deﬁnition - Business Case
When an organisation’s leadership does not fully comprehend the advantages that
result from a Cloud Native migration, providing a strong Business Case will allow
them to understand and support the project without hesitation.
A company is experiencing pressure from external advisors or internal tech teams
to move to Cloud Native. The executive team is contemplating making the move to
CN, but this is the first such transformation the company has undertaken and there
is only a partial understanding of the complexity of a CN migration and the benefits
that will come from it.

In This Context:
The benefits of the transformation are not clear to the executive team, so they may not support the
initiative or even give it serious consideration.
- The traditional model is for organisations to be massively risk averse, to minimise uncertainty at all
costs.
- Change-averse culture avoids new technologies or experimental approaches.
- Cloud Native architectures are conceptually different from traditional approaches, merging careful
up-front planning with flexible and mutable,experimentation-based implementation.
- Tech teams are eager to get started with the transformation, even before business case is
established

Therefore:
Create a formal business case to help educate the organisation’s executive team,
taking into account the benefits to be gained from Cloud Native. The business
case needs to include key CN advantages, including acceleration of business
velocity, scalability, potential cost savings, and enhanced recruitment and retention
of tech staff.

Consequently:
The business case for a CN transformation is clear and the company’s decision
makers have a clear understanding of the advantages CN confers and are ready
to move forward. They are prepared to allocate the necessary budget and
resources that such a large project will require.

Deﬁnition - Microservices Architecture
To reduce the costs of coordination between teams delivering large monolithic
applications, build the software as a series of microservices that are built,
deployed and operated independently.
A company has decided to move to Cloud Native and is looking at the ways to
increase the velocity of feature development and to optimise their utilization of
cloud resources. The size of the development/engineering staff can range from a
few tens, for a small to medium business, up to a few thousand for a large
enterprise.

In This Context:
Delivery of large monolithic applications developed by large teams require long and complex coordination
and extensive testing, leading to longer TTM (Time to Market). Hardware utilisation by such applications is
inefficient, which leads to waste of resources.
- People tend to delay painful moments; since integration and delivery are typically painful, their
frequency tends to decrease as system longevity increases.
- Larger monolithic systems are increasingly more difficult to understand as they grow in size and
complexity
- Monoliths are easier to work with than modular applications so long as they are small enough to be
understood by each developer.
- Conway’s law: architecture tends to resemble the organisational structure.

Therefore:
Split applications into smaller microservices that can be built, tested, deployed
and run independently from other components.
- Independent components allow different teams to make progress at their own
pace faster-moving teams are not held back by slower ones and to use the
most appropriate tools for each situation.
- Independence and freedom of choice are achieved in a tradeoff with reduced
standardisation and certain types of reusability.

Consequently:
New systems are created from a large number of small components with a
complex web of connections.
Small and independent teams work on separate modules and deliver them with
only limited coordination across the teams.

Related Patterns:
Cross-functional teams, CI, CD, Common Services, Libraries & Tools,
Communication Through API, Dynamic Scheduling.

Scenarios That Create Tension
Common Bad Conﬁgurations

Patterns and the Maturity Matrix
Writing Your Own Story

Conclusion
Finding Your Own QWAN

Thanks

container-solutions.com info@container-solutions.com Container Solutions KPIs @containersoluti

Cloud Native Patterns (Jamie Dobson, Container Solutions)

More Related Content

Similar to Cloud Native Patterns (Jamie Dobson, Container Solutions) (20)

More from London Microservices (8)

Recently uploaded (20)

Cloud Native Patterns (Jamie Dobson, Container Solutions)