Serverless Diary: Your Way to A Successful Event-Driven Architecture

Serverless Diary: Your Way to A Successful Event-Driven Architecture

Serverless Diary: Your Way to A Successful Event-Driven Architecture. Event-driven architecture (EDA) can be seen as a way of wiring all your microservices together. The understanding of core principles of event-driven architecture and demonstrates how to use them in your serverless architecture.

I. Introduction

Carrying on from where I left sharing my experience of implementing microservices in a serverless style in my previous blogs, the focus of this blog is to understand how to approach event-driven design. This blog takes the understanding of core principles of event-driven architecture and demonstrates how to use them in your serverless architecture.

II. What and Why of Event-Driven Architecture

Event-driven architecture (EDA) can be seen as a way of wiring all your microservices together. In this architecture, a microservice publishes an event when something notable happens, such as when it updates a business entity. Other microservices subscribe to those events. When a microservice receives an event it can update its business entities, which might lead to more events being published.

In the last decade, event-driven architectures have gained more popularity as more organizations and businesses have moved to the cloud. In the context of serverless cloud-native architectures, where the goal is to move to more managed services without worrying about manual intervention for scaling your infrastructure, I find event-driven architecture usage more compelling because of the following benefits:

  • Automatic Scaling — Since individual components in your serverless landscape are capable of auto-scale. Bottlenecks due to increased load or traffic are identified and taken care of automatically by the virtue of managed service usage, wherein only your affected component auto-scales and not your entire infrastructure.
  • Asynchronous style Communication — avoids all bottlenecks caused by synchronous architectures where an increase in traffic is proportional to the responsiveness of your application.
  • Decoupled — Each microservice/component can be independently developed, tested, and deployed, helping with business agility and speed to market.

microservices aws architecture

Bootstrap 5 Complete Course with Examples

Bootstrap 5 Tutorial - Bootstrap 5 Crash Course for Beginners

Nest.JS Tutorial for Beginners

Hello Vue 3: A First Look at Vue 3 and the Composition API

Building a simple Applications with Vue 3

Deno Crash Course: Explore Deno and Create a full REST API with Deno

How to Build a Real-time Chat App with Deno and WebSockets

Convert HTML to Markdown Online

HTML entity encoder decoder Online

Serverless Vs Microservices Architecture - A Deep Dive

Companies need to be thinking long-term before even starting a software development project. These needs are solved at the level of architecture: business owners want to assure agility, scalability, and performance.

The Service Mesh in the Microservices World - DZone Microservices

In this article, take a look at the service mesh in the microservices world. The software industry has come a long journey and throughout this journey, Software Architecture has evolved a lot. Starting with 1-tier (Single-node), 2-tier (Client/ Server), 3-tier, and Distributed are some of the Software Architectural patterns we saw in this journey.

What Is a Microservice Architecture? Why Is It Important Now?

Microservices are growing as the default architectural design pattern. But why has it become such a point of emphasis? Find out here.

Architecture Suggestion | AWS, Spring Boot, Microservices

This video covers an architecture suggestion for a viewer's question on designing a CRM System 💥Join TechPrimers Slack Community

Testing Microservices Applications

In this article, look at different ways to test microservices and how you can have a suitable testing strategy to begin with.