O11y Architecture - Financial Calculations Example

Cloud native technology has been changing the way payment services are architected. In 2020 I presented a series with insights from real implementations adopting open source and cloud native technology to modernize payment services. 

The series consisted of six articles and covered architectural diagrams from logical, schematic, to detailed views of the various  use cases uncovered. 

The architectures presented were based on open source cloud native technologies, such as containers, microservices, and a Kubernetes based container platform. The major omission in this series was to avoid discussing any aspect of cloud native observability. This series will take a look at fixing that omission with an open source standards based cloud native observability platform that helps DevOps teams control the speed, scale, and complexity of a cloud native world for their financial payments architecture.

The part one introduction covered the baseline architecture, defined the payments project, and shared the planning for this series in adding observability to the logical and physical architectures. Part two explored the common architectural elements needed when adding cloud native observability to your financial payments solutions. Part three discussed a physical architecture view of a financial payments example sharing insights into how to deploy your cloud native observability at scale. 

In this article we'll walk through a financial calculations physical architecture, exploring how to add scalable cloud native observability and laying out the various deployment options you have for your financial calculations observability solution.

O11y Architecture - Financial Payments Example

Cloud native technology has been changing the way payment services are architected. In 2020 I presented a series with insights from real implementations adopting open source and cloud native technology to modernize payment services. 

The series consisted of six articles and covered architectural diagrams from logical, schematic, to detailed views of the various  use cases uncovered. 

The architectures presented were based on open source cloud native technologies, such as containers, microservices, and a Kubernetes based container platform. The major omission in this series was to avoid discussing any aspect of cloud native observability. This series will take a look at fixing that omission with an open source standards based cloud native observability platform that helps DevOps teams control the speed, scale, and complexity of a cloud native world for their financial payments architecture.

The part one introduction covered the baseline architecture, defined the payments project, and shared the planning for this series in adding observability to the logical and physical architectures. Part two explored the common architectural elements needed when adding cloud native observability to your financial payments solutions. In this article we'll walk through a financial payments physical architecture, exploring how to add scalable cloud native observability and laying out the various deployment options you have for your payments observability solution.

O11y Architecture - Financial Payments Common Observability Elements

Cloud native technology has been changing the way payment services are architected. In 2020 I presented a series with insights from real implementations adopting open source and cloud native technology to modernize payment services. 

The series consisted of six articles and covered architectural diagrams from logical, schematic, to detailed views of the various  use cases uncovered. 

The architectures presented were based on open source cloud native technologies, such as containers, microservices, and a Kubernetes based container platform. The major omission in this series was to avoid discussing any aspect of cloud native observability. This series will take a look at fixing that omission with an open source standards based cloud native observability platform that helps DevOps teams control the speed, scale, and complexity of a cloud native world for their financial payments architecture.

The part one introduction covered the baseline architecture, defined the payments project, and shared the planning for this series in adding observability to the logical and physical architectures. In this article we'll explore the logical diagram that captures the elements of a successful payments solution.

O11y Architecture - Financial Payments Introduction

Back in September 2020 I was researching open source architectures, meaning looking at several customer solutions from my employer at the time and developing a generic view of these solutions for certain use cases.

One of the use cases is known as financial payments and back in 2020 I kicked off a series covering this architecture with the article Payments architecture - An introduction. The series consisted of six articles and covered architectural diagrams from logical, schematic, to detailed views of the various  use cases we uncovered. 

The architectures presented were based on open source cloud native technologies, such as containers, microservices, and a Kubernetes based container platform. The major omission in this series was to avoid discussing any aspect of cloud native observability. 

This series will take a look at fixing that omission with an open source standards based cloud native observability platform that helps DevOps teams control the speed, scale, and complexity of a cloud native world for their financial payments architecture.

Devoxx UK 2022 - Designing Your Best Architectural Diagrams (video)

 Devoxx UK 2022 conference a week ago has posted recordings of all the sessions. I wanted to share our workshop session on how to start designing your best architectural diagrams

The Devoxx series is well know and I've attended and spoken at multiple sessions for the Belgian version in the past. It's very developer centric with a lot of good depth and knowledgable attendees.

Below you'll find the video recording of this 30 minute session and links to the free online workshop and slides used in this talk.

Devoxx UK 2022 - Designing Your Best Architectural Diagrams (slides)

Today I presented at Devoxx UK 2022 conference and shared our workshop on how to start designing your best architectural diagrams

The Devoxx series is well know and I've attended and spoken at multiple sessions for the Belgian version in the past. It's very developer centric with a lot of good depth and knowledgable attendees.

In London I was presenting a short introduction to our diagram tooling, freely hosted online and here are the introduction slides.

London OpenShift User Group - Talking Architecture Shop

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.

Portfolio Architecture Examples - Application Development Collection

 

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.

Portfolio Architecture Examples - Data Engineering Collection

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.

Portfolio Architecture Examples - Retail Collection

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.

Portfolio Architecture Examples - Finance Collection

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.

DevOpsDays Raleigh 2022 - Talking Architecture Shop (slides)

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.

Portfolio Architecture Examples - Infrastructure Collection

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.

Portfolio Architecture Examples - Automation Collection

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.

Portfolio Architecture Examples - Edge Collection

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.

Portfolio Architecture Examples - Telco Collection

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.

Portfolio Architecture Examples - Healthcare Collection

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.

DevConf.US 2022 - Talking more architecture shop

DevConf.US 2022 the 5th annual, free, technology conference for community project and professional contributors to Free and Open Source technologies was a few weeks ago. 

The plans are to again bring this back to an in person event later this summer, August 18-20 in Boston, MA.

For the first time in years I am not part of the selection committee and therefore wanted to take this opportunity to share our teams progress over the last year with the talks in our series Talking Architecture Shop. 

Devoxx UK 2022 - Designing Your Best Architectural Diagrams (accepted)

As mentioned previously, I've pushed a few talks to the Devoxx UK 2022 conference being held from 11-13 of May in London.

The Devoxx series is well know and I've attended and spoken at multiple sessions for the Belgian version in the past. It's very developer centric with a lot of good depth and knowledgable attendees.

The selection committee decided that the workshop I submitted would fit their developer tools and productivity theme nicely so I'll be sharing this great material with you in London.

DevOpsDays Raleigh 2022 - Talking Architecture Shop (accepted)

 I've mentioned previously that I was trying to join the DevOpsDays Raleigh 2022 conference this year, to be hosted on April 13-14 in Raleigh, NC. 

I submitted a few talks, a workshop, and crossed my fingers to await the selection committee results.

The verdict is in, I've got a session talking architecture shop selected. It's going to be fun to share my teams research and development of open source DevOps architectures.

Here's the talk and abstract and really looking forward to seeing you all in person!