Talking Architecture Shop - Exploring Open Source Success at Scale
•Download as PPTX, PDF•
1 like•168 views
You've heard of large scale open source architectures, but have you ever wanted to take a serious look at these real life enterprise implementations that scale? This session takes attendees on a tour of multiple use cases covering enterprise challenges like integration, optimisation, cloud adoption, hybrid cloud management, healthcare, retail, manufacturing, financial services, and much more. Not only are these architectures interesting, but they are successful real life implementations featuring open source technologies and power many of your own online experiences. The attendee departs this session with a working knowledge of how to map general open source technologies to their solutions. Material covered is available freely online and attendees can use these solutions as starting points for aligning to their own solution architectures. Join us for an hour of power as we talk architecture shop!
Recommended
Recommended
More Related Content
Similar to Talking Architecture Shop - Exploring Open Source Success at Scale
Similar to Talking Architecture Shop - Exploring Open Source Success at Scale (20)
More from Eric D. Schabell
More from Eric D. Schabell (20)
Recently uploaded
Recently uploaded (20)
Talking Architecture Shop - Exploring Open Source Success at Scale
- 1. Talking Architecture Shop Eric D. Schabell Portfolio Architect Technical Director May 2022 https://bit.ly/talking-architecture-shop Paul Vergilis Integration Solutions Architect @pverge1 Debezium, Kafka,Camel Exploring Open Source Success at Scale
- 5. 3+ Rooms Cottage, Farmhouse, Colonial Specific Named Floor Plans (“The Huntley” or “The Winstead”) Increase SqFt, Curve Staircase, etc. Engineering ensures it’s built to code HOME ARCHITECTURAL DESIGN PORTFOLIO 3+ Red Hat Products IT A&M, Hybrid Cloud, Cloud-Native Specific Named Solution Plans (“Edge Medical Diagnosis” or “Supply Chain Integration”) Adjust configuration/services utilized Consulting/Support/Engineering determine supportability Requirements: Style: Model: Customizations: Supportability: PORTFOLIO ARCHITECTURE Design Implementation
- 6. These architectures are providing a common repeatable process, visual language and tool set, presentations, and architecture diagrams. These document customer deployments of three or more open source technologies that continuously advance successful customer use cases. TALKING ARCHITECTURE SHOP Demos Customer research Enablement & Presentations Presentation Videos Diagrams Publications Solution Brief
- 7. CUSTOMER VALUE PORTFOLIO ARCHITECTURE :: Customer Value ● Gives customers a known good implementation design for Red Hat solutions ● Illustrates how customers can combine Red Hat solutions to solve business problems ● Open Source tooling allows customization from baseline template
- 8. Server image build Source repository Cloud Adoption Introduction Remote management and automation Consistency of RHEL estate across all public clouds and datacenters Quickly scale cloud deployments Red Hat platform Business Drivers Customers environment Hybrid cloud environment Automation Orchestration Smart Management Red Hat platform Red Hat host Red Hat host Automation Orchestration Smart Management Red Hat platform Server transfer Infrastructure code repo Stage release Infrastructure code repo Image repo Red Hat Software as a Service
- 9. Omnichannel Customer Experience Introduction Distributed deployments, non- centralized integration Data management, security, and user access Multiple protocol support through different integration technologies Business Drivers Customer Single- sign-on Internal Systems Data Storage 3rd-Party Services External Platform Backend Systems Applications API Management Business Processes Supplier Partner Vendor Container Platform Front-end Services Service Integration Data Integration
- 10. Payments Introduction Generation of real-time payments data for analytics Better transparency into actual account balances Improved ability to monitor payments for fraud Business Drivers Customers Routing services External payments service Payment Network Data cache Payments API Clearning services Payment applications Container Platform Payments events Anti-money laundering services Fraud detection services Validation services
- 11. Business goals Rules repository Business Optimisation Introduction Improve efficiency of planning problem challenges Consistency of planning results across stores and businesses Remove manual changes and colleagues from planning problems Business optimisation Business Drivers Container platform Results Business processes External data, resources, hard and soft constraints External 3rd-party systems Planning problem solving External triggers Business process Internal local systems Internal remote systems Integration services Microservices Internal triggers Internal data, resources, hard and soft constraints
- 12. Developer Build Pipeline Cloud Native Development Introduction Consistent enterprise image registry strategy Consistent development workflow for local and remote container platform Hybrid cloud development and deployment strategy Business Drivers Developer tooling Container Platform (Build) Transient Images Container Platform (Enterprise Registry) Sandbox Images Enterprise Images Cloud Platforms Dev Infrastructure Test Infrastructure Prod Infrastructure Dev Images Test Images Production Images Applications Microservices Applications Microservices Applications Microservices 3rd-Party Images Red Hat Images
- 13. THREE LEVELS OF ARCHITECTURE Logical view High level abstractions of services and platforms. No networking or data flows. Service descriptions can be added. Schema / Physical Describes the main nodes and services and their interactions and network connections. Product details can be included. Cardinality and logical groupings can be described. Node or Service detail Detailed look at one specific service. Includes deployment mode, storage and networking details. TALKING ARCHITECTURE SHOP
- 15. Portfolio Architecture CLOUD-NATIVE DEPLOYMENT CI / CD platform oc client Dev infrastructure Test infrastructure Prod infrastructure Enterprise registry
- 16. Portfolio Architecture CLOUD-NATIVE DEPLOYMENT (ENTERPRISE) CI / CD platform oc client, docker, podman Dev infrastructure Test infrastructure Prod infrastructure Enterprise registry Pull images: Docker, Poidman, Skopeo, Mirrors
- 17. TALKING ARCHITECTURE SHOP DETAIL: ENTERPRISE REGISTRY OpenShift Container Platform image registry managing trusted images: ▸ Red Hat Quay managed registry ▸ Trusted images in registry ▸ Input from: ･ Sandbox registry (trusted) ▸ Output to: ･ Test image registry ･ Production image registry
- 19. MORE INFORMATION TALKING ARCHITECTURE SHOP Red Hat Portfolio Architecture Center https://www.redhat.com/architect/portfolio Portfolio Architecture Examples https://gitlab.com/osspa/portfolio-architecture-examples Portfolio Architecture Diagram Tool https://www.redhat.com/architect/portfolio/tool/index.html Portfolio Architecture Workshops Complete workshop on using the tool. More than recommended that you go through this workshop. Learn how to build a portfolio architecture with this beginners guide workshop.
- 20. CONFIDENTIAL designator V0000000 linkedin.com/company/red-hat youtube.com/user/RedHatVideos facebook.com/redhatinc twitter.com/RedHat Red Hat is the world’s leading provider of enterprise open source software solutions. Award- winning support, training, and consulting services make Red Hat a trusted adviser to the Fortune 500. Thank you
Editor's Notes
- Talking Architecture Shop - Exploring Open Source Success at Scale You've heard of large scale open source architectures, but have you ever wanted to take a serious look at these real life enterprise implementations that scale? This session takes attendees on a tour of multiple use cases covering enterprise challenges like integration, optimisation, cloud adoption, hybrid cloud management, healthcare, retail, manufacturing, financial services, and much more. Not only are these architectures interesting, but they are successful real life implementations featuring open source technologies and power many of your own online experiences. The attendee departs this session with a working knowledge of how to map general open source technologies to their solutions. Material covered is available freely online and attendees can use these solutions as starting points for aligning to their own solution architectures. Join us for an hour of power as we talk architecture shop! https://bit.ly/talking-architecture-shop
- Architecture is not hard, or is it… we all have the best intentions but having a good plan does not always mean it’s going to work out the way you draw it up… (Photo: https://unsplash.com/photos/fteR0e2BzKo)
- You must be thinking…. How did that happen? (Photo: https://www.reddit.com/r/NotMyJob/comments/54wdx0/built_the_staircase_exactly_as_designed_boss/)
- Imagine if you have a plan based on others who’ve built this before you? Would that help? Enter Portfolio Architectures, providing proven value: Giving organizations proven implementation designs for open source solutions Illustrating how organizations can combine open source solutions to solve business problems High level architecture as a guide with flexibility for existing architecture choices (Photo: https://unspalsh.com)
- Our portfolio architectural designs are much like a home’s architectural design. When building a portfolio architecture, there’s a number of commonalities between our process, and that of a home builder: Just as in order to consider something a home, it would require rooms such as a bedroom, living area, kitchen and bathroom - we also require at least three Red Hat products to consider it a Portfolio Architecture. Where there are different styles of homes, we align our architectures to the different Pillars/Sales Conversations Our team has created the floor plans for you, so you take the packaged floor plan to ---Once we’ve chosen a style, we choose a specific plan within that style that closest aligns with our customers business needs. At this point, the PA team has created something useful for you to present to your customer, and further refactor the design to fit their exact implementation. Customizations and Supportability would be handled outside of this team as our designs are taken to the field, and further worked on by the account teams, services, etc.
- Building consistent and useful architecture diagrams is challenging. As the product portfolio grows we are providing clear and reusable portfolio architectures for use with our partners and customers.
- Shorten the sales cycle by understanding the customer problem and selecting the best Red Hat and partner ecosystem solutions based on their use case, roles, and the sales conversation. Make the solution more relevant by only introducing features or products that address the customers specific needs. Introduce customers to new areas of the portfolio that otherwise might not be evaluated. Holistic approach instead of product focused. Free up the field account team’s and partner’s time to focus on the customer problem/solution by reusing well defined and proven solution architectures that can be tailored for the customer. Background information - ( speaker notes). Current scenario for many portfolio sales engagements includes pulling in BU TMMs or PMMs to explain their product. This has the risk of delaying the sales cycle by introducing features that are not required by the customer or by introducing competition between our own products. Customers that are confused by why they need certain features or products due to well intentioned but conflicting BU messages will delay buying or may cause them to look for other “simpler” solutions.
- Introduction to the business drivers and solution story for use case: Accelerating cloud adoption with effective automation for deploying and managing workloads across multiple cloud infrastructures according to performance, security, compliance, and cost requirements.
- Introduction to the business drivers and solution story, with use case: Omnichannel implies integration and orchestration of channels such that the experience of engaging across all the channels someone chooses to use.
- Introduction to the business drivers and solution story for the use case: Financial institutions enabling customers with fast, easy to use, and safe payment services available anytime, anywhere…
- Introduction to the business drivers and solution story.
- Introduction to the business drivers and solution story.
- Three levels of the diagrams produced for a portfolio architecture; logical, physical, and detailed.
- This is the logical view of the application integration architecture as deployed within a container-based platform cluster. (Click here to load this diagram in the design tooling) Developer Developer IDE: the developer environment. Source code management: online or local to enterprise, git code repository for example. Fuse Integration Services: provides a set of tools and containerized images that enable development, deployment, and management of integration microservices within OpenShift. Development frameworks: development tooling and frameworks, such as Java runtime, Camel Spring Boot, etc. Container platform CI/CD Registry management: Skopeo, a tool for copying containers and images between different types of container storage. It can copy containers from one container registry to another. CI/CD platform: such as Jenkins, an automation server, helping to automate building, testing, and deploying, facilitating continuous integration and continuous delivery. Container platform services Messaging services: queue and topic messaging services. Caching microservices: services supporting data caching and data grid functions. Decision microservices: services for decision management using deployed decision management services. Customer microservices: customer centric data shaping services. Process microservices: services for orchestration using deployed process automation services. Integration data microservices: Providing abstraction between front end services and internal storage. Integration microservices: Providing abstraction between front end services and external systems. Infrastructure services API management: Manage and expose APIs for microservice and application interface availability. Single-sign-on (SSO) server: Single-Sign-On server. Storage services Block storage: traditional storage or cached realization of logical or cloud-based storage definitions as needed by applications, processes, and services. In this case traditional Oracle databases. Object-based storage: Software-defined storage definitions for container-based applications, processes, and services. In this case Gluster container-native storage.
- Example of a cloud-native deployment with a developer working on a stack and pushing work to the CI / CD platform using OpenShift client tooling [1]. The CI / CD platform takes the code and initiates a source-to-image workflow [2] building the container image to specification provided in a build configuration. When the build completes, a dev image is tagged and placed into a transient image registry [3] that collects development images. The central enterprise registry is managed by Red Hat Quay, pulling development images into the enterprise registry as they become available [4] and pushes them out to the development infrastructure image registry (Dev cluster) [5] for further deployment and testing [6]. As testing passes in the development infrastructure using CI / CD platform, the image is then tagged for testing and pulled into the enterprise registry [7]. All test tagged images are then pushed to the test infrastructure clusters image registry [8] for further deployment and testing [9]. Finally, after testing passes in CI / CD platform for testing infrastructure the image is then tagged for production and pulled into the enterprise registry [10]. All production tagged images are then pushed to the prod infrastructure clusters image registry [11] for further deployment and use [12]. (Click here to load this diagram in the design tooling)
- Example of a cloud-native deployment with a developer working on a stack and pushing work to the CI / CD platform using their preferred tooling, such as OpenShift client tooling [1]. The CI / CD platform takes the code and initiates building the container image to specification. When the build completes, a dev image is tagged and placed into a transient image registry [2] that collects development images. The central enterprise registry is managed by Red Hat Quay, pulling development images into the sandbox registry as they become available [3]. Here in the sandbox registry all untrusted and third-party images are collected for testing before exposing them to the organization beyond development infrastructure. The sandbox development image is pushed out to the development infrastructure cluster image registry [5] for further deployment and testing [6]. As testing passes in the development infrastructure using CI / CD platform (this might include for example security checks), the image is then tagged for testing and pulled into the enterprise registry [7]. All test tagged images are then pushed to the test infrastructure clusters image registry [8] for further deployment and testing [9]. Finally, after testing passes in CI / CD platform for testing infrastructure the image is then tagged for production and pushed to the production infrastructure cluster image registry [10] for further deployment and use [11]. (Click here to load this diagram in the design tooling)
- The detailed view of this element provides an overview, description, technologies, and covers the calls being made to and from it. (Click here to load this diagram in the design tooling)
- A public facing architecture center is available for all.
- Where to go for more information.
- Talking Architecture Shop - Exploring Open Source Success at Scale You've heard of large scale open source architectures, but have you ever wanted to take a serious look at these real life enterprise implementations that scale? This session takes attendees on a tour of multiple use cases covering enterprise challenges like integration, optimisation, cloud adoption, hybrid cloud management, and much more. Not only are these architectures interesting, but they are successful real life implementations featuring open source technologies and power many of your own online experiences. The attendee departs this session with a working knowledge of how to map general open source technologies to their solutions. Material covered is available freely online and attendees can use these solutions as starting points for aligning to their own solution architectures. Join us for an hour of power as we talk architecture shop! https://bit.ly/talking-architecture-shop-at-scale