Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Using containers to build a microservices architecture

1,603 views

Published on

Microservices are more than just building software. There are questions around architecture, your organization, processes and your way of thinking. Innovation does not come naturally to everyone, so let's explore the journey you need to take as you leverage your current architecture and learn how the foundational building blocks to microservices are containers.

Event site: https://www.redhat.com/en/about/events/containers-enterprise-red-hat-virtual-event

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Using containers to build a microservices architecture

  1. 1. Using Containers to Build a Microservices Architecture Eric D. Schabell
  2. 2. THE JOURNEY Are you doing microservices today? Architecting the future Containers as the foundation 2
  3. 3. We need to innovate, not just keep up… (Red Queen’s Race) 3
  4. 4. Not innovative... targeting efficiency 4Source: Dave Gray, The Connected Company
  5. 5. Value delivered through services, not just mass production of product. 5
  6. 6. 6 To deliver services which provide value, we need to listen and react. We need to deal with variety.
  7. 7. Driving innovation through IT 7 Decentralized decision making Purpose driven Innovation: admit you don’t have all the answers figure out how to ask the right questions
  8. 8. 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….
  9. 9. 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.
  10. 10. ARCHITECTING THE FUTURE 10
  11. 11. “Organizations which design systems ... are constrained to produce designs which are copies of the communication structures of these organizations.” -- Melvin Conway 11
  12. 12. 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
  13. 13. Break things down (organizations, teams, IT systems, etc) down into smaller pieces for greater parallelization and focus on reducing time to value. 13
  14. 14. 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
  15. 15. 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
  16. 16. CONTAINERS AS THE FOUNDATION 16
  17. 17. 17 Remember, microservices is about optimizing… ...for speed
  18. 18. 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
  19. 19. 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/packaging 19
  20. 20. 20 OPEN INNOVATION LABS COLLABORATION Space to work, innovate, and discuss RESIDENCY An eight-week accelerated teaming engagement COMMUNITY INCUBATION Communities supporting innovation
  21. 21. FUTURE OPPORTUNITIES 21 Install OpenShift Container Platform in minutes https://github.com/redhatdemocentral/ocp-install-demo Red Hat Demo Central - App Dev in the Cloud examples https://github.com/redhatdemocentral Book: Microservice for Java Developers https://developers.redhat.com/promotions/microservices-for-java-developers Learn more about Red Hat Summit at redhat.com/summit
  22. 22. THANK YOU 22

×