Introducing event-driven architectures

Till now we have been working and understanding Lambda using our trusty calculator example code, that simply accepts few parameters and values as inputs, and, when run, provides you with some desired output. What you may not have noticed is that the inputs that we were providing for the code to run were actually part of an event, that would trigger the code into running. Similarly, you can write Lambda functions that get activated or triggered when a particular message or event is generated. This is perhaps one of the biggest reasons why I love Lambda so much and why Lambda is so much better than your traditional EC2 instances! But, before we begin exploring the various triggers and events that Lambda can respond to, let us understand what Event Driven architectures are all about and how are they so useful.

Event-driven architecture (EDA) is basically a software architecture pattern that deals with the generation, detection, consumption, and reaction...