Sure, microservices event driven architecture is something in which services communicate with the assistance of events. If a service does an activity that can be of interest to other services, an event is produced. This event is a record of that activity. Different services consume such events, and this is done to perform their tasks.

To better answer this question, there are several factors that need to be taken note of in an organization/platform. This includes its overall size, future growth plans, scalability needs, and team expertise. The general notion is that by moving to a microservices architecture, you will encounter autonomy, flexibility, and scalability. But you may have to deal with added infrastructure requirements and other complexities.

In simple terms, this is an architectural approach to creating software applications as a group of independently deployable, loosely coupled, and small services. Every service in the architecture is created to do a particular type of business functionality.