Understanding Event-Driven Architecture
In any application, everything can be divided into events. Events are triggered either by some interaction with an external actor (either another application or a user) or by other events. An application is basically the triggering of multiple sequences of events to perform some sort of function. Google Drive, for example, is an application, and its function is just storage. Of course, this is an oversimplification and there are a lot of things that go into storing, organizing, and serving files, but that is the basic gist of it. It functions based on a series of events, each of which comes from a certain source.
Now, different events require different technologies, frameworks, and libraries within the system to interact with each other in perfect harmony. When this harmony is naturally achieved, it is a thing of beauty...