Using containers to build a microservices architecture

Preview:

Citation preview

Using Containers to Build a Microservices Architecture

Eric D. Schabell

THE JOURNEY

Are you doing microservices today?Architecting the futureContainers as the foundation

2

We need to innovate, not just keep up…(Red Queen’s Race)

3

Not innovative... targeting efficiency

4Source: Dave Gray, The Connected Company

Value delivered through services, not just mass production of product.

5

6

To deliver services which provide value, we need to listen and react. We need to deal with variety.

Driving innovation through IT

7

Decentralized decision makingPurpose drivenInnovation:

admit you don’t have all the answersfigure out how to ask the right questions

8

“People try to copy Netflix, but they can only copy what they see. They copy the results, not the process.”

-- Adrian Cockcroft, former Chief Cloud Architect, Netflix

You don’t need to worry about Netflix, you need to be afraid of the barbershop….

So… are you doing microservices today?

9

Maybe it doesn’t matter so much… What we really care about is speed, reduced time to value, and business outcomes.

ARCHITECTING THE FUTURE

10

“Organizations which design systems ... are constrained to produce designs which are copies of the communication structures of these organizations.”

-- Melvin Conway

11

As defined by Red Hat

“Microservices is an architectural approach, that emphasizes the decomposition of applications into single-purpose, loosely coupled services managed by cross-functional teams, for delivering and maintaining complex software systems with the velocity and quality required by today’s digital business” 12

Break things down (organizations, teams, IT systems, etc) down into smaller pieces for greater

parallelization and focus on reducing time to value.

13

Why break things down?Single, self-contained, autonomous, isolated and Resilient to faults

Faster software delivery and own their own data

Easier to understand individually

Scalability

Right technology for the problem

Test individual services

Individual deployments 14

Are you doing microservices today?

Using self-service infrastructure and application automation...

Have working CI/CD...

Have health checking, monitoring, instrumentation...

Have logging, distributed tracing...

Able to release services independently...

Honoring backward and forward compatibility...

So…

15

CONTAINERS AS THE FOUNDATION

16

17

Remember, microservices is about optimizing… ...for speed

Are you doing microservices today?

Using cloud enabled self-service infra..

Using cloud enabled self-service application automation...

Have working CI/CD to your private cloud...

Have health checking, monitoring, instrumentation in your cloud...

Able to release services independently...

Honoring backward and forward compatibility...

So…

18

The answer should start with...OpenShift Container Platform

Team self service application deployment, CLI/IDE/Web based tooling

Developer workflow, build/deployment triggers, Jenkins Pipeline out of the box

Enterprise focused (LDAP, RBAC, Oauth, Kubernetes,etc)

Integrated container registry

Software Defined Networking (SDN)

Container native format/packaging19

20

OPEN INNOVATION LABS

COLLABORATIONSpace to work,

innovate, and discuss

RESIDENCYAn eight-week accelerated

teaming engagement

COMMUNITY INCUBATIONCommunities

supporting innovation

FUTURE OPPORTUNITIES

21

Install OpenShift Container Platform in minuteshttps://github.com/redhatdemocentral/ocp-install-demo

Red Hat Demo Central - App Dev in the Cloud exampleshttps://github.com/redhatdemocentral

Book: Microservice for Java Developershttps://developers.redhat.com/promotions/microservices-for-java-developers

Learn more about Red Hat Summit at redhat.com/summit

THANK YOU

22

Recommended