Eric D. Schabell

The Ultimate Beginners Guide to Rules and Processes

2023-03-03T07:00:00.005+01:00

There are so many ways and so much content out there to get you started with open source rules and process automation tooling by Red Hat, so where do you start?

The goal of this guide is to provide you with a learning path through this content as a way to get started from download, to installation, to quick starts, to hands-on workshops, and all the way to using this technology for your cloud-native development projects.

You'll walk away from this guide with a learning path mapped out through content that's enjoyable to work with and can help you get started on your rules and process automation projects today.

There is a way to start from the beginning and walk a path to rules and process automation proficiency, outlined as follows:

Choosing the rules or process automation path
Obtain the tooling (downloads)
Quick start projects (installs, cloud-native, demos)
Published content collections
Video collections
Free hands-on workshops

To get started on your learning path just explore the outline below:

(As seen on KieLive episode #14)

Saying goodbye to Red Hat

2022-07-08T07:00:00.001+02:00

My tenure: 2009-2022

The time has come... the end of my tenure at Red Hat after +13 years.

How about a short summary of some of the highlights while at Red Hat before I move on to a new adventure?

I'll try to capture the big milestones, but there are just so many that I'm sure to miss a few.

It's a moment of reflection on more than a decade spent in the world of enterprise open source technologies and riding a wave that was Red Hat in the prime of its evolution in the industry.

I have been involved in open source since my introduction late in life to programming, operating systems, and Linux in 1996. Before joining Red Hat I was involved in the community around a business process management project called jBPM. We were using this heavily in the financial institution I was working at and I became active as you do when you submerge yourself into an open source technology.

In those days it was still jBPM 3 and we were having the time of our lives learning to model and implement processes. We even went crazy with a jBPM exception framework, to just give you an example of what we thought was possible back in those days.

It all led to Red Hat knocking on my door in 2009 to join the Netherlands team as their first middleware (JBoss) solution architect.

At the time I joined I remember the SA team was about 15 associates across Europe, Red Hat had around 2000 associates world wide, and the stock price was between $22-$24 (later sold to IBM for $190).

It was incredible fun and there was a very active start up feel to what we were doing. My experiences with JBoss technologies and specifically the Business Rules Management System (BRMS) led to me spending more time across Europe helping other sales teams than in my own region. I was also still active in the community around those products, meaning Drools, jBPM, and other JBoss projects upstream.

This role I held for approximately three years before the product orgnanization came knocking. My contacts in the product teams led to my being asked to join the Middleware Business Unit as one of their first MW Technical Marketing Managers or TMM. At this time I think we had like 4-5 products so one person could manage the role. I ended up spending around four years in this role and we grew not only our MW product portfolio, but the team eventually grew out to five TMM's before I moved on.

We worked on products like JBoss SOA-P, Switchyard, JBoss Virtualization, JBoss BPM Suite, the first versions of OpenShift (remember gears?), and so much more. This role required enablement sessions being delivered to the field and we visited all our regional offices; APAC (Singapore, Tokyo, Beijing), EMEA (Munich, London, Stockholm, Madrid, Amsterdam, Brussels, Rome, Warsaw, etc), NA (Boston, Dallas, Raleigh, Mountain View, Portland, St. Louis, Tampa, etc), and LATAM (Mexico City, San Paulo, etc).

Right at the end of that role I got the chance to move to the US, out on an island off the coast of North Carolina for a year. Quite the adventure and my family loved every minute of our island time.

The next role to come along was in a brand new business unit, called the Integrated Solutions Business Unit, setup to try and pull together the first multi-product products for our field to sell. I spent the next two years working with some serious rock stars as we pulled together Red Hat Cloud Infrastructure and Red Hat Cloud Suite products. I was the TMM for both of these, and due to our PMM leaving before the launch of the Red Hat Cloud Suite I picked up the PMM work for the product launch.

Part of this period also involved the setting up of the internal Red Hat TMM Practice, where all existing and new TMM's could find a baseline on how to be effective in their roles. We also worked with Red Hat HR and developed a well defined ladder for the creation of the official TMM role in Red Hat.

My final role was to help setup a new concept, that of the Portfolio Architecture team. We have spent the last four years defining, researching, receiving field feedback, and creating 25 published architectures that you can explore on the Red Hat Portfolio Architecture Center. This team started with just three of us, but has since grown out to seven and I had the honour of being the technical director of this developing product.

All along this journey through Red Hat I've spent many hours mentoring all manner of TMM's (and other associates) as I am a true believer that we all have something to share to make others better.

I never suspected how long this would last when I walked into that first interview and they asked me to draw a SOA architecture on a whiteboard. I look around now 13 yrs, 106 days later and I'm still engaged at Red Hat.

Now this brings me to the part were we say goodbye and thank you all for the fun we've had together. There are so many colleagues that have become both friends and family, so it's not even possible to name them (but you know who you are). My last day is next week Friday, 15 July.

What's next you ask?

Stay tuned for more on that after I take a break between the old and the new.

London OpenShift User Group - Talking Architecture Shop

2022-05-10T17:00:00.013+02:00

My second trip this year takes me to London for some fun later this week at Devoxx UK 2022 and a chance to speak with our customers at the London OpenShift User Group.

As the official site says, Tuesday 10th May we have a special meeting of the London OpenShift User Group featuring:

Enterprise Portfolio Architecture - the open source way
Uncover the genius within your ranks - A live stream of the Keynote presentation from Red Hat Summit in Boston featuring Paul Cormier (President and CEO), Stefanie Chiras (Senior VP) and Matt Hicks (Executive VP)

Below you'll find the slides from my talk.

The event kicks off with a welcome and then I'll present the following, with slides included here for your viewing pleasure:

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.

Thanks for the time and lending me your ears!

Portfolio Architecture Examples - Application Development Collection

2022-05-09T07:00:00.105+02:00

Figure 1: The portfolio architecture process

For a few years now we've been working on a project we have named Portfolio Architectures. These are based on selecting a specific use case we are seeing used in the real world by customers and then finding implementations of that case using three or more products from the Red Hat portfolio.

This basic premise is used as the foundation, but many aspects of open source are included in both the process and the final product we have defined. There is a community, where we share the initial project kickoff with a group of architects and use their initial feedback from the start. We also present the architecture product we've created right at the end before we publish to ensure usability by architects in the field. The final publish product includes some internal only content around the customer projects researched, but most of the content is open and freely available through various open source channels.

This article is sharing an overview of the product we've developed, what's available to you today in our architecture center, and concludes by sharing a collection of architectures we've published.

Introduction

The basis of a portfolio architecture is a use case, two to three actual implementations that can be researched, and includes the use of a minimum of three products. This is the ideal foundation for a project to start, but we encountered a problem with use cases containing emerging technologies or emerging domains in the market. To account for these we've chosen to note the fact that these are opinionated architectures based on internal reference architectures.

The product has been defined as complete for publishing when it contains the following content:

Short use case definition
Diagrams - logical, schematic (physical), and detail diagrams
Public slide deck containing the use case story and architecture diagrams
Internal slide deck containing both the public deck content and the confidential customer research
Video (short) explanation of the architecture
Either a technical brief document or one or more articles covering the solution architecture

Note that the items in italics are all available to anyone in the Red Hat Portfolio Architecture Center or in the Portfolio Architecture Examples repository.

Figure 2: Logical diagram design template
Tooling and workshops

The progress towards our products required a good idea of how we wanted to diagram our architectures. We chose to keep them very generic and simple in style to facilitate all levels of conversation around a particular use case without getting bogged down in notational discussions.

A simple three level design for our architectures was captured by using logical, schematic, and detail diagrams. All of these have been integrated in open source tooling with pre-defined templates and icons for easily getting started. Furthermore, we've developed a tooling workshop to quickly ramp up on the design methods and tooling we've made available. It's called Designing Your Best Architectural Diagrams, has been featured in several conferences around the world.

Application development collection

The collection featured today is centered around architectures supporting application development and cloud development. There are currently fifteen architectures in this collection and we'll provide a short overview of each, leaving the in depth exploration as an exercise for the reader.

Figure 3: Application development architecture collection

In each of these architecture overviews you'll find a table of contents outlining the technologies used, several example schematic diagrams with descriptions, and a link in the last section to open the diagrams directly into the online tooling in your browser.

Business optimisation

Retail is the process of selling consumer goods or services to customers through multiple channels of distribution to earn a profit. Retailers satisfy demand identified through a supply chain. The term retailer is typically applied where a service provider fills the small orders of many individuals, who are end-users, rather than large orders of a small number of wholesale, corporate or government clientele.

The use case is optimising delivery routing, automating rostering of staff, and improving efficiency of tasks across multiple stores.

Cloud native development

Cloud native development is an approach to building and running applications to fully use the advantages of the cloud computing model (i.e., responsive, elastic, and resilient applications). Red Hat empowers organizations to build and run scalable applications in modern, dynamic environments such as public, private, and hybrid clouds.

Containers and orchestration, DevOps and continuous delivery, microservices and service meshes, and declarative application programming interfaces (APIs) are key building blocks of cloud-native application development. These technologies and techniques deliver loosely coupled systems that are resilient, manageable, and observable. Combined with robust automation, they allow businesses to make high-impact application improvements frequently and predictably with minimal effort and risk. Additionally, cloud native architecture and technologies provide the foundation for newer development models such as serverless computing and Functions-as-a-Service.

The use case is an approach to building and running applications to fully exploit the advantages of the cloud computing model (i.e. responsive, elastic and resilient applications).

Designing an omnichannel customer experience

An omnichannel approach provides a unified customer experience across platforms, creating a single view for customers to interact with their own information.

Red Hat provides a foundation for IT teams to develop and deliver omnichannel services through a combination of integration and process automation technologies. Agile integration defines how organizations are transforming and delivering on their digital promise to customers by integrating applications and services across on-premise infrastructure and cloud environments. Business automation, in the form of process integrations, are captured to enable access to complex process services.

The use case for omnichannel implies integration and orchestration of channels such that the experience of engaging across all the channels someone chooses to use.

Edge medical diagnosis

This architecture covers edge medical diagnosis in the healthcare industry. It Accelerates medical diagnosis using condition detection in medical imagery with AI/ML at medical facilities.

The use case is accelerating medical diagnosis using condition detection in medical imagery with AI/ML at medical facilities.

Headless e-commerce

Retail is the process of selling consumer goods or services to customers through multiple channels of distribution to earn a profit. The term electronic commerce (e-commerce) refers to a business model that allows companies and individuals to buy and sell goods and services over the Internet.

The use case is deploying a container based e-commerce website while moving away from tightly coupled existing e-commerce platform.

Integrating with SaaS applications

Integrating with Software-as-a-Service (SaaS) applications is the process of operationally connecting SaaS solutions to other separate computer systems or applications into a single larger system, allowing each solution to functionally work together.

The use case is providing integration with SaaS applications, platforms, and services empowers organizations to build and run scalable applications in modern, dynamic environments such as public, private, and hybrid clouds.

Intelligent Data as a Service (iDaaS)

Intelligent DaaS (Data as a Service) is about building and delivery of systems and platforms in a secure and scalable manner while driving data needs for moving towards consumerisation in healthcare. Feel free to explore this portfolio architecture by clicking on the diagram below.

The use case is Intelligent Data as a Service (iDaaS) is about building and delivery of systems and platforms in a secure and scalable manner while driving data needs for moving towards consumerisation in healthcare.

Modernising testing with data synthesis

Data synthesis is about enabling innovation with a focus around enabling massive amounts of data to be available for business users and developers needs in a secure and scalable manner.

The use case is modernising testing with data synthesis, a testing innovation with focus around enabling massive amounts of data to be available for both business users and developers in a secure and scalable manner.

Open banking

Financial services institutions understand that today’s banking customers expect fast, easy-to-use services they can tap into anytime, anywhere, and are therefore accelerating adoption of digital technologies to enable a variety of new offerings.

(Note: this project is a new architecture and currently in progress, so sharing one of the schematic architecture diagrams and you can monitor this project for updates as it progresses to completion.)

The use case is a cloud ready, modular open source approach offering a wide range of technology options and allows low-effort integration covering all aspects of an Open Banking implementation.

Payments

An offering of (near) real-time payments lets businesses, consumers, and even governments send and accept funds that provide both availability to the recipient and instant confirmation to the sender. Enabling real-time - or at least faster - payments that improve the speed of online payment experiences to customers has the potential to give banks a greater opportunity to win, serve, and retain their customers. By building solutions that capture real-time payment business, banks also can drive higher payment volumes, ideally at lower costs as well as engage new customer segments.

The use case examines financial institutions enabling customers with fast, easy to use, and safe payment services available anytime, anywhere.

Point of sale

Retail is the process of selling consumer goods or services to customers through multiple channels of distribution to earn a profit. A point of sale, or point of purchase, is where you ring up customers. When customers check out online, walk up to your counter, or pick out an item from your stand or booth, they're at the point of sale. Your point-of-sale system is the hardware and software that enables your business to make those sales.

The use case is simplifying and modernising central management of distributed point-of-sale devices with built in support for container based applications.

Real-time stock control

Retail is the process of selling consumer goods or services to customers through multiple channels of distribution to earn a profit. Real-time inventory management is an automated process of recording sales and purchases through the use of software. It gives you a complete picture of what's happening with inventory, allowing your business to react quickly to supply chain needs.

The use case is providing (near) real-time stock positions and dynamic pricing promotions information to retailer omnichannels.

Retail data framework

Retail is the process of selling consumer goods or services to customers through multiple channels of distribution to earn a profit. A data framework refers to the process of managing enterprise retail data. The framework or system sets the guidelines and rules of engagement for business and management activities, especially those that deal with or result in the creation and manipulation of data.

The use case is creating a framework for access to retail data from customers, stock, stores, and staff across multiple internal teams.

Store health and safety

Retail is the process of selling consumer goods or services to customers through multiple channels of distribution to earn a profit. Store health and safety is all about managing risks to protect workers and stores. In a global context, health and safety is also an essential part of the movement towards sustainable operational growth.

The use case is managing effective in-store compliance, health & safety, and employee checks and procedures.

Supply chain integration

Retail is the process of selling consumer goods or services to customers through multiple channels of distribution to earn a profit. Supply chain integration is a large-scale business strategy that brings as many links of the chain as possible into a closer working relationship with each other. The goal is to improve response time, production time, and reduce costs and waste.

The use case is streamlining integration between different elements of a retail supply chain for on-premise, cloud, and other third-party interactions.

If you are interested in more architecture solutions like these, feel free to explore the Portfolio Architecture Examples repository. More architecture collections include:

Portfolio Architecture Examples - Data Engineering Collection

2022-05-02T07:00:00.033+02:00

Figure 1: The portfolio architecture process

This article is sharing an overview of the product we've developed, what's available to you today in our architecture center, and concludes by sharing a collection of architectures we've published.

Introduction

The product has been defined as complete for publishing when it contains the following content:

Short use case definition
Diagrams - logical, schematic (physical), and detail diagrams
Public slide deck containing the use case story and architecture diagrams
Internal slide deck containing both the public deck content and the confidential customer research
Video (short) explanation of the architecture
Either a technical brief document or one or more articles covering the solution architecture

Note that the items in italics are all available to anyone in the Red Hat Portfolio Architecture Center or in the Portfolio Architecture Examples repository.

Figure 2: Logical diagram design template
Tooling and workshops

Data engineering collection

The collection featured today is centered around architectures leveraging data engineering concepts and tooling. There are currently eight architectures in this collection and we'll provide a short overview of each, leaving the in depth exploration as an exercise for the reader.

Figure 3: Data engineering architecture collection

Cloud to edge

This architecture covers the use case of providing a consistent infrastructure experience from cloud to edge and enabling modern containerized applications at edge.

This use case is bringing cloud like capabilities to the edge locations.

Data center to edge

This architecture covers the use case around data center to edge where the energy (utility) infrastructure companies operate across vast geographical area that connects the upstream drilling operations with downstream fuel processing and delivery to customers. These companies need to monitor the condition of pipeline and other infrastructure for operational safety and optimization.

The use case is bringing computing closer to the edge by monitoring for potential issues with gas pipelines (edge).

Edge manufacturing efficiency

The manufacturing industry has consistently used technology to fuel innovation, production optimization and operations. Now, with the combination of edge computing and AI/ML, manufacturers can benefit from bringing processing power closer to data. This helps actions be taken faster on things like errors and predictive maintenance.

The use case is for boosting manufacturing efficiency and product quality with artificial intelligence and machine learning out to the edge.

Edge medical diagnosis

This architecture covers edge medical diagnosis in the healthcare industry. It Accelerates medical diagnosis using condition detection in medical imagery with AI/ML at medical facilities.

The use case is accelerating medical diagnosis using condition detection in medical imagery with AI/ML at medical facilities.

Intelligent Data as a Service (iDaaS)

Payments

The use case examines financial institutions enabling customers with fast, easy to use, and safe payment services available anytime, anywhere.

Retail data framework

The use case is creating a framework for access to retail data from customers, stock, stores, and staff across multiple internal teams.

SCADA interface modernisation

This Portfolio Architecture targets energy providers in North America that need to be compliant with NERC regulations and in order to achieve this they decide to modernise the interfaces between their business applications and their SCADA systems also for a better consumption of information that can be used in combination with AI/ML and decision management tools to better address customer needs.

The use case is providing interfaces with SCADA systems that are compliant with NERC regulations, creating different layers of API gateways to protect business service depending on the network zones.

If you are interested in more architecture solutions like these, feel free to explore the Portfolio Architecture Examples repository. More architecture collections include:

Portfolio Architecture Examples - Retail Collection

2022-04-25T07:00:00.133+02:00

Figure 1: The portfolio architecture process

This article is sharing an overview of the product we've developed, what's available to you today in our architecture center, and concludes by sharing a collection of architectures we've published.

Introduction

The product has been defined as complete for publishing when it contains the following content:

Short use case definition
Diagrams - logical, schematic (physical), and detail diagrams
Public slide deck containing the use case story and architecture diagrams
Internal slide deck containing both the public deck content and the confidential customer research
Video (short) explanation of the architecture
Either a technical brief document or one or more articles covering the solution architecture

Note that the items in italics are all available to anyone in the Red Hat Portfolio Architecture Center or in the Portfolio Architecture Examples repository.

Figure 2: Logical diagram design template
Tooling and workshops

Retail collection

The collection featured today is centered around architectures in the retail industry. There are currently seven architectures in this collection and we'll provide a short overview of each, leaving the in depth exploration as an exercise for the reader.

Figure 3: Retail architecture collection

Business optimisation

The use case is optimising delivery routing, automating rostering of staff, and improving efficiency of tasks across multiple stores.

Headless e-commerce

The use case is deploying a container based e-commerce website while moving away from tightly coupled existing e-commerce platform.

Point of sale

The use case is simplifying and modernising central management of distributed point-of-sale devices with built in support for container based applications.

Real-time stock control

The use case is providing (near) real-time stock positions and dynamic pricing promotions information to retailer omnichannels.

Retail data framework

The use case is creating a framework for access to retail data from customers, stock, stores, and staff across multiple internal teams.

Store health and safety

The use case is managing effective in-store compliance, health & safety, and employee checks and procedures.

Supply chain integration

The use case is streamlining integration between different elements of a retail supply chain for on-premise, cloud, and other third-party interactions.

If you are interested in more architecture solutions like these, feel free to explore the Portfolio Architecture Examples repository. More architecture collections include:

Portfolio Architecture Examples - Finance Collection

2022-04-18T07:00:00.068+02:00

Figure 1: The portfolio architecture process

This article is sharing an overview of the product we've developed, what's available to you today in our architecture center, and concludes by sharing a collection of architectures we've published.

Introduction

The product has been defined as complete for publishing when it contains the following content:

Short use case definition
Diagrams - logical, schematic (physical), and detail diagrams
Public slide deck containing the use case story and architecture diagrams
Internal slide deck containing both the public deck content and the confidential customer research
Video (short) explanation of the architecture
Either a technical brief document or one or more articles covering the solution architecture

Note that the items in italics are all available to anyone in the Red Hat Portfolio Architecture Center or in the Portfolio Architecture Examples repository.

Figure 2: Logical diagram design template
Tooling and workshops

Finance collection

The collection featured today is centered around architectures in the financial services industry. There are currently two architectures in this collection and we'll provide a short overview of each, leaving the in depth exploration as an exercise for the reader.

Figure 3: Finance architecture collection

Open banking

The use case is a cloud ready, modular open source approach offering a wide range of technology options and allows low-effort integration covering all aspects of an Open Banking implementation.

Payments

The use case examines financial institutions enabling customers with fast, easy to use, and safe payment services available anytime, anywhere.

If you are interested in more architecture solutions like these, feel free to explore the Portfolio Architecture Examples repository. More architecture collections include:

DevOpsDays Raleigh 2022 - Talking Architecture Shop (slides)

2022-04-13T20:00:00.005+02:00

I've mentioned previously that I had a talk accepted to the DevOpsDays Raleigh 2022 conference this year.

Today was the day after travel to Raleigh that we got to chat with a room of super enthusiastic architects.

Thanks for the time and lending us your ears. Below you'll find the talk title and abstract along with the slides for your viewing pleasure.

My session is from a series called Talking Architecture Shop. This is focusing on architecture research for solutions in the DevOps domain that scale and will be co-presented with my good friend Ricardo Garcia Cavero.

Talking Architecture Shop - Exploring Open Source DevOps 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 DevOps implementations that scale? This session takes attendees on a tour of multiple use cases covering DevOps challenges with hybrid cloud management with GitOps, DevOps in healthcare, 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!

Portfolio Architecture Examples - Edge Collection

2022-03-31T07:00:00.123+02:00

Figure 1: The portfolio architecture process

This article is sharing an overview of the product we've developed, what's available to you today in our architecture center, and concludes by sharing a collection of architectures we've published.

Introduction

The product has been defined as complete for publishing when it contains the following content:

Short use case definition
Diagrams - logical, schematic (physical), and detail diagrams
Public slide deck containing the use case story and architecture diagrams
Internal slide deck containing both the public deck content and the confidential customer research
Video (short) explanation of the architecture
Either a technical brief document or one or more articles covering the solution architecture

Note that the items in italics are all available to anyone in the Red Hat Portfolio Architecture Center or in the Portfolio Architecture Examples repository.

Figure 2: Logical diagram design template
Tooling and workshops

Edge collection

The collection featured today focuses on edge computing architectures. There are currently five architectures in this collection and we'll provide a short overview of each, leaving the in depth exploration as an exercise for the reader.

Figure 3: Edge architecture collection

Cloud to edge

This architecture covers the use case of providing a consistent infrastructure experience from cloud to edge and enabling modern containerized applications at edge.

This use case is bringing cloud like capabilities to the edge locations.

Data center to edge

The use case is bringing computing closer to the edge by monitoring for potential issues with gas pipelines (edge).

Edge manufacturing efficiency

The use case is for boosting manufacturing efficiency and product quality with artificial intelligence and machine learning out to the edge.

Edge medical diagnosis

This architecture covers edge medical diagnosis in the healthcare industry. It Accelerates medical diagnosis using condition detection in medical imagery with AI/ML at medical facilities.

The use case is accelerating medical diagnosis using condition detection in medical imagery with AI/ML at medical facilities.

SCADA interface modernisation

The use case is providing interfaces with SCADA systems that are compliant with NERC regulations, creating different layers of API gateways to protect business service depending on the network zones.

If you are interested in more architecture solutions like these, feel free to explore the Portfolio Architecture Examples repository. More architecture collections include:

Portfolio Architecture Examples - Telco Collection

2022-03-29T07:00:00.022+02:00

Figure 1: The portfolio architecture process

This article is sharing an overview of the product we've developed, what's available to you today in our architecture center, and concludes by sharing a collection of architectures we've published.

Introduction

The product has been defined as complete for publishing when it contains the following content:

Short use case definition
Diagrams - logical, schematic (physical), and detail diagrams
Public slide deck containing the use case story and architecture diagrams
Internal slide deck containing both the public deck content and the confidential customer research
Video (short) explanation of the architecture
Either a technical brief document or one or more articles covering the solution architecture

Note that the items in italics are all available to anyone in the Red Hat Portfolio Architecture Center or in the Portfolio Architecture Examples repository.

Figure 2: Logical diagram design template
Tooling and workshops

Telco collection

The collection featured today is centered around architectures in the telco domain. There are currently three architectures in this collection and we'll provide a short overview of each, leaving the in depth exploration as an exercise for the reader.

Figure 3: Telco architecture collection

Telco 5G core: on premise

5G is the latest evolution of wireless mobile technology that aims to enable the delivery of highly immersive experiences for people and ultra reliable, low latency communication between devices. At the heart of each 5G network lies the 5G Core (5GC).

This portfolio architecture conceives 5G Core as a set of disaggregated, cloud native applications that communicate internally and externally over well defined standard interfaces. Each 5GC component is implemented as a container-based application and is referred to as cloud-native network function (CNF).

The use case is ultra-reliable, immersive experiences for people and objects when and where it matters most.

Telco 5G with hyperscalers

5G is the latest evolution of wireless mobile technology. In this portfolio architecture we’ll discuss an 5G solution built with open source technologies at core, that can work across any hyperscaler.

The use case is building an adaptable, on-demand infrastructure services for 5G Core that can deliver across diverse use cases with minimal CAPEX and OPEX.

Telco radio access networks

5G is the latest evolution of wireless mobile technology. It can deliver a number of services from the network edge:

Enhanced mobile broadband (eMBB)
- 5G enhances data speeds and experiences with new radio capabilities like mmWave frequency spectrum for higher bandwidth allocation and theoretical throughput up to 20Gbps.
Ultra-reliable, low-latency communication (uRLLC)
- 5G supports vertical industry requirements, including sub-millisecond latency with less than 1 lost packet in 105 packets.
Massive machine type communications (mMTC)
- 5G supports cost-efficient and robust connection for up to 1 million mMTC, NB-IOT, and LTE-M devices per square kilometer without network overloading.

The use case is base on the facts that digital transformation of mobile networks is accelerating and cloudification is increasing. Following the core network, radio access network (RAN) solutions are now taking advantage of the benefits of cloud computing.

If you are interested in more architecture solutions like these, feel free to explore the Portfolio Architecture Examples repository. More architecture collections include:

Eric D. Schabell

The Ultimate Beginners Guide to Rules and Processes

Saying goodbye to Red Hat

London OpenShift User Group - Talking Architecture Shop

Talking Architecture Shop - Exploring Open Source Success at Scale

Portfolio Architecture Examples - Application Development Collection

Introduction

Figure 2: Logical diagram design templateTooling and workshops

Application development collection

Portfolio Architecture Examples - Data Engineering Collection

Introduction

Figure 2: Logical diagram design templateTooling and workshops

Data engineering collection

Portfolio Architecture Examples - Retail Collection

Introduction

Figure 2: Logical diagram design templateTooling and workshops

Retail collection

Portfolio Architecture Examples - Finance Collection

Introduction

Figure 2: Logical diagram design templateTooling and workshops

Finance collection

DevOpsDays Raleigh 2022 - Talking Architecture Shop (slides)

Talking Architecture Shop - Exploring Open Source DevOps at Scale

Portfolio Architecture Examples - Edge Collection

Introduction

Figure 2: Logical diagram design templateTooling and workshops

Edge collection

Portfolio Architecture Examples - Telco Collection

Introduction

Figure 2: Logical diagram design templateTooling and workshops

Telco collection

Figure 2: Logical diagram design template
Tooling and workshops

Figure 2: Logical diagram design template
Tooling and workshops

Figure 2: Logical diagram design template
Tooling and workshops

Figure 2: Logical diagram design template
Tooling and workshops

Figure 2: Logical diagram design template
Tooling and workshops

Figure 2: Logical diagram design template
Tooling and workshops