BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Event Driven Architecture Content on InfoQ

  • Event Streams and Workflow Engines – Kafka and Zeebe

    In a recent joint meeting in Amsterdam, Kai Waehner described features of Apache Kafka, a distributed streaming platform, and how it fits in an Event-Driven Architecture. Bernd Rücker described how workflow engines can handle complex business processes, and discussed how Zeebe, a new highly scalable workflow engine, can be used with Kafka.

  • In a Serverless World, We Still Need State

    Today there is a large push in enterprise architecture towards serverless architecture. Jonas Bonér argues that although he strongly believes in the serverless movement, the programming model should not focus only on stateless functions. We must also have a focus on state, allowing us to benefit from the advantages of serverless while building distributed general-purpose applications.

  • Build a Monolith before Going for Microservices: Jan de Vries at MicroXchg Berlin

    Most developers don’t work at global large-scale companies like Netflix. Most developers work in much smaller companies with maybe up to 50 – 80 developers, Jan de Vries noted in his presentation at MicroXchg Berlin, where he argued that a properly built monolith in many cases is superior to a microservices based architecture. With a well-built monolith, it will also be easy to pull services out.

  • Creating Events from Databases Using Change Data Capture: Gunnar Morling at MicroXchg Berlin

    When you store data in a database, you often also want to put the same data in a cache and a search engine. The challenge is how to keep all data in sync without distributed transactions and dual writes. One way is to use a change data capture (CDC) tool that captures all changes made. In a presentation at MicroXchg Berlin, Gunnar Morling described Debezium, an implementation of CDC using Kafka.

  • A Critical Look at Event-Driven Systems: Bernd Rücker at QCon London

    There is currently a hype in adoption of event-driven systems. Sometimes they are almost seen as the “magic thing” in our strive for decoupled systems, Bernd Rücker noted at the recent QCon London 2019. In his presentation he took a critical look at three common hypotheses around event-driven systems: events decrease coupling, Orchestration needs to be avoided, and Workflow engines are painful.

  • The Importance of Event-First Thinking

    For global businesses to meet today’s architectural challenges with constant change and extreme scale, we need to go back to the basic principles of system design. The common element in the problems we face is the notion of events driving both actions and reactions, Neil Avery writes in a series of blog posts describing why events are so important and the advantages of an event-first approach .

  • Microsoft Announces Several Updates to Azure Event Grid

    Microsoft has announced multiple updates to Azure Event Grid, which allows for creating event-driven application architectures. The announcement includes features around retry policies, dead lettering capabilities, Azure Storage Queues and Hybrid Connections as a destination for events, and a manual validation handshake.

  • Are Frameworks Good or Bad, or Both?

    Preferring frameworks or libraries is somewhat controversial, Frans van Buul, Evangelist at AxonIQ, the company behind Axon Framework, writes in a recent blog post. Many argue in the favour of libraries but Van Buul thinks that a framework can be very valuable when building business applications. He believes this to be especially true for applications based on CQRS, DDD and event sourcing.

  • Experiences Moving from Microservices to Workflows at Jet.com

    The Order Management System (OMS) at Jet was originally developed using a collection of microservices orchestrating tasks. As the company grew, the challenges with this architecture also grew until they decided to build a new workflow-based platform. In a blog post, James Novino at Jet describes the challenges with their old system and an overview of the new platform.

  • Microsoft Expands the Availability of Azure Service Bus and Event Hubs

    In a recent blog post, Microsoft announced Availability Zones support for Azure Service Bus Premium and Azure Event Hubs Standard. With the support, customers will have a high availability option for these services in availability zones supported regions.

  • Amazon Announces New Integrations for AWS Step Functions

    Amazon has announced new integrations with their compute, database, messaging, analytics, and machine learning services for AWS Step Functions, allowing to leverage these as steps in the state machine workflows. With AWS Step Functions, an abstracted way is provided to connect and coordinate activities, taking advantage of a highly scalable runtime.

  • Microsoft Updates Azure Event Grid with Event Domains, Advanced Filtering Features and More

    With Event Grid, customers can manage all their event in one place in Azure. Recently, Microsoft announced enhancements to this service with two new features, advanced filters, and Event Domains. Furthermore, the team responsible for Event Grid has been working to improve the developer experience, and has made Event Grid available in more regions.

  • Russ Miles: Ignored Architects and Chaos Engineering

    At the recent Event-Driven Microservices Conference in Amsterdam, Russ Miles claimed that the biggest challenge for an architect is that you get ignored. You have great ideas like event-driven microservices, but the reaction too often is that it sounds good, but that it’s overly complicated for the needs at hand.

  • Axon Conference Panel: Why Should We Use Microservices?

    In the panel discussion at the recent Event-Driven Microservices Conference in Amsterdam, Frans van Buul from AxonIQ, the conference organizer, started by noting that microservices are quite mainstream today. He wanted to look back at what we have learned, but also think about where we will be heading in the next couple of years.

  • NATS Messaging System Gets Kafka-Like Log API via Liftbridge

    Joining the hot event-driven technology space is Liftbridge, an open-source project that extends the NATS messaging system with a scalable, Kafka-like log API. InfoQ spoke to creator Tyler Treat to learn more about the project, and the changing nature of data integration.

BT