This is an article from DZone’s 2022 Enterprise Application Integration Trend Report.
For more:
In the echo chambers of application development, we constantly hear the mantra « API-first, » but this slogan has a fundamental flaw: APIs should typically be the last choice when building a distributed application. The correct war cry ought to instead be: « APIs outside, events inside. »
The rise of data in motion in the insurance industry is visible across all lines of business, including life, healthcare, travel, vehicle, and others. Apache Kafka changes how enterprises rethink data. This blog post explores use cases and architectures for event streaming. Real-world examples from Generali, Centene, Humana, and Tesla show innovative insurance-related data integration and stream processing in real-time.
Most insurance companies have similar challenges:
In this article, I am going to be talking about how we can define your event-driven architectures using the AsyncAPI definition.
A while ago, I published an article about how you can document REST APIs using Open API 3 specification. This was for synchronous APIs.
Before OOP languages, the programmer would control how the program is executed and that would be from the app’s main routine. In modern programming, that control is delegated to the external non-main loops, and the main routine becomes an event-loop that waits for events to occur and then executes it with the relevant event handler.
This new model of programming (it has been around since the 70s though) is called event-driven programming.
Developers are working with new applications every day using Apache Kafka as the backbone to implement an event-driven architecture (EDA) to support distributed systems. However, this adds new challenges when sharing across teams, even within the same organization. What endpoints are available? What is the structure of the message? That’s why payload examples became critical to speed up development. For this reason, having a reliable and enterprise-grade service to mock Apache Kafka should be an item in your EDA checklist. This post will do a quick review of the Microcks General Availability (GA) version and their support to Kafka.
Last week kicked off the Red Hat Summit 2020 virtual event. It’s amazing to imagine that so many people decided to sign up and attend this free event over the next two days.
For me it’s a chance to share some ideas that my friend Christina Lin and I have been working on for some time, advanced integration blueprints.
