 |
| Figure 1: The portfolio architecture process |
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 |
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.
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 |
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.
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.
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.
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.
If you are interested in more architecture solutions like these, feel free to explore the Portfolio Architecture Examples repository. More architecture collections include: