Architectural diagrams hardcover7/2/2023 ![]() ![]() The architecture collection provided insights into all manner of use cases and industries researched between 2019-2022. Your engineering and observability teams are still using the same open-source tooling, query languages, and visualization that they are well versed in from their experiences with CNCF projects such as Prometheus and OpenTelemetry. The managed Chronosphere observability platform allows you to host your cloud-native observability needs, unplugging from your DIY infrastructure, and redirecting your open-source standards ingestion of metrics and telemetry data. Many organizations start off their cloud-native observability journey with do-it-yourself (DIY) solutions that, over time due to the payments solution success, grow into a resource burden in management, infrastructure, and observability data complexity. Many are not under the full hosted control of the financial organization, and this is where you find the SaaS solution for your observability needs. The elements found in the external systems capture the various regional or local needs for a payments solution. I'll also present several specific use cases and provide schematic diagrams that detail the physical architectures for those use cases. In upcoming articles in this series, I'll share the specific ways you can deploy and leverage the Chronosphere Collector element in a container environment. This provides for a very easy transition for organizations that might have started their cloud-native observability journey using open-source projects and standards. Using open source standards and protocols from the CNCF projects Prometheus and OpenTelemetry, it's collecting telemetry data and metrics data, and routing them to an external Chronosphere observability platform. In this article, I'll focus on introducing the logical view of only the component layers where I'm adding cloud-native observability elements to the solution. In the article " Payments Architecture - Common Architecture Elements," I toured the generic architecture and outlined the common elements of payments architecture. The goal here is to describe generic components and outline a few specific cases enabling you to make the right choices when applying to your own architecture.įeel free to comment or contact me directly with your feedback. You're more than capable of slotting in the technologies and components you've committed to in the past where applicable. The assumption is that you're smart and can figure out adapting it to your own architecture. The intent was to provide architectural guidance and not in-depth technical details. ![]() ![]() These elements presented here are, then, the generic common architectural elements identified and raised up to a generic architecture. In this article, we'll explore the logical diagram that captures the elements of a successful payment solution.īefore diving into the common elements, please understand that this is a collection of identified elements uncovered in multiple working implementations. The introductory article (part one, linked in the "Series Overview" section at the conclusion of this post) covered the baseline architecture, defined the payments project, and shared the planning for this series in adding observability to the logical and physical architectures. 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 major omission in this series was to avoid discussing any aspect of cloud-native observability. ![]() The architectures presented were based on open-source cloud-native technologies, such as containers, microservices, and a Kubernetes-based container platform. The series consisted of six articles and covered architectural diagrams from logical and schematic to detailed views of the various use cases uncovered. In 2020, I presented a series of insights from real implementations adopting open-source and cloud-native technology to modernize payment services. Cloud-native technology has been changing the way payment services are architected. ![]()
0 Comments
Leave a Reply. |