Retail data framework – Common architectural elements

article imageIn our previous article from this series we introduced a use case around the data framework for retail stores.

The process was laid out how we've approached the use case and how portfolio solutions are the base for researching a generic architectural blueprint.

The only thing left to cover was the order in which you'll be led through the blueprint details.

Are Automated APIs the future? Podcast With Zdenek ā€œZā€ Nemec

In 2020, APIs are an essential part of any digital transformation toolkit. Whether youā€™re looking to deliver new products, expand your marketing reach, analyze your data, innovate on existing technologies, or improve work efficiency ā€” modern enterprises rely on APIs to get things done.

However, as API adoption explodes, the complexity of discovery, consumption, and integration also gets dialed to eleven. When APIs have to be integrated and maintained manually, this places an additional burden on an already overwhelmed IT department. Superface.ai Co-Founder and CTO Zdenek Nemec explain how automation can change the way we develop and approach APIs and how description formats such as OpenAPI and AsyncAPI help make APIs be more discoverable.

Webinar – Hybrid cloud for financial services series features payments architecture

Next month we're taking a tour of how to improve your competitive advantage with hybrid cloud infrastructure supporting your financial services.

It's a two part series where first we dive into the strategies, business benefits, and possible approach for your hybrid cloud journey. Second, we'll dig a bit deeper at implementing effective architectures for cloud native development, leveraging the best practices from successful payments architectures, and look at how to modernizing existing payments architectures.

Payments Architecture – Fraud Detection Example

Cloud technology is changing the way payment services are architectured. In this series we will be presenting insight from our customers on adopting open source and cloud technology to modernize their payment service.So far we've presented research-based architectural blueprints of omnichannel customer experience, integrating with SaaS applications, and cloud-native development solutions.  

In the previous article in this series we walked through the anti-money laundering physical architecture. 

Integrating With SaaS Applications ā€” An Introduction

Kubernetes service balancerSince introducing the first architecture blueprint focused on omnichannel integration, we've been looking at how to integrate with Software as a Service (SaaS) applications.

It's an interesting challenge in that we've been given the mission of creating architectural content based on common customer adoption patterns. That's very different from most of the traditional marketing activities usually associated with generating content for the sole purpose of positioning products for solutions. When you're basing the content on actual execution in solution delivery, you're cutting out the chaff. What's that mean?   

It means that it's going to provide you with a way to implement a solution using open source technologies by focusing on the integrations, structures, and interactions that actually have been proven to work. What's not included are any vendor promises that you'll find in normal marketing content. Those promised that when it gets down to implementation crunch time, might not fully deliver on their promises.

Enter the term Architectural Blueprint.  

Integration Key to Experience: Container Platform Essentials (Part 5)

In my previous article from this series, we looked into the details that determine how your integration becomes the key to transforming your customer experience.

It started with laying out the process of how I've approached the use case by researching successful customer portfolio solutions as the basis for a generic architectural blueprint. Now it's time to cover various blueprint details.Image title

Integration Key to Experience: API Management Details (Part 4)

In my previous article from this series, we started diving into the details that determine how your integration becomes the key to transforming your customer experience.

It started with laying out the process of how I've approached the use case by researching successful customer portfolio solutions as the basis for a generic architectural blueprint. Now it's time to cover various blueprint details.