Establishing a Foundation

By Abhijeet Gole
 Reduce Cost: Will this reduce overall cost of designing,
implementing, and maintaining IT services?

Increase Release Speed: Will this increase the speed at which

Goals for the my team can get from idea to deployment of services?

Microservices
Way Improve Resilience: Will this improve the resilience of our
service network?

Enable Visibility: Does this help me better see what is going on

in my service network?
 The ability to reduce the cost of designing, implementing, and
deploying services

Reduce Allows you more flexibility when deciding whether to create a

cost
service at all.

For example, if the work of creating a new service component

includes three months of design and review, six months of
coding and testing, and two more weeks to get into
production, that’s a very high cost—one that you would likely
think very carefully about before starting.
Increase release speed

A more useful way to view this goal is that you want to

shorten the time between idea and deployment.

By automating important elements of the deployment

cycle, you can speed up the whole process of getting
services into production.

Automating release can go a long way toward increasing

the speed of your microservice implementation.
 No matter the speed or cost of solutions, it is
also important to build systems that can
“stand up” to unexpected failures.

Improve One of the ways DevOps practices has

focused on improving resilience is through
resilience the use of automated testing.

By making testing part of the build process,

the tests are constantly run against checked-
in code, which increases the chances of
finding errors in the code.
 Enable visibility

The DevOps practices of

logging and monitoring are
To improve the ability of
great examples of this level of
stakeholders to see and
runtime visibility. Etsy’s John
understand what is going on in
Allspaw has said, “If it moves
the system.
graph it. If it matters, alert on
it”.
 Platforms

SHARED CAPABILITIES LOCAL CAPABILITIES

 Culture

Culture is important because it not only sets the tone for the way
people behave inside an organization, but it also affects the output
of the group.

The code your team produces is the result of the culture.

 Culture

• Research shows that the way your teams communicate (both to each other
Communication and toother teams) has a direct measurable effect on the quality of your
software.

Team alignment • The size of your teams also has an effect on output. More people on the team
means essentially more overhead.

Fostering innovation • Innovation can be disruptive to an organization but it is essential to growth

and long-term success.
Summary

• we’ve reviewed the common set of platform

capabilities called Cockcroft’s “microservices
concerns” and cited examples of how a number of
organizations provide these platform capabilities to
their teams.
• The way your teams communicate, their size, and
the level of innovation you support within those
teams have a significant effect on the quality of
their output.
• Understood what is required to actually implement
a microservice architecture