Event-driven
The advantages of using event-driven architecture for AWS and GCP integrations.
Last updated
The advantages of using event-driven architecture for AWS and GCP integrations.
Last updated
The term event-driven refers to a software architecture in which an application or system responds to specific events or actions generated by a user, another application, or a system. In an event-driven architecture, the application or system does not perform a task until it receives an event or action that triggers it to do so.
Event-driven applications are designed to respond to events in real-time, making them highly responsive to changes in the environment. In this architecture, events are the primary communication mechanism between the various components of the system.
When an event is triggered, the application or system can take immediate action, such as sending a notification, updating a database, or invoking a function. By using event-driven architectures, developers can build applications that are more user-friendly, responsive, and scalable.
Using event-driven integration allows Firefly to fetch your assets in near real-time continuously. Firefly integrates with CloudTrail for AWS and uses audit logs from Google Cloud to refresh the assets in the Inventory as soon as they change. Without it, the Inventory takes up to eight hours to update.
To use the event-driven service, you must enable CloudTrail in your AWS account, which is available with Terraform and CloudFormation. For Google Cloud, enable logging API.
When you enable S3 event notifications for Terraform state files, Firefly can monitor updates to your IaC stacks stored in S3 buckets and optimize the IaC status in the system. This will provide near real-time updates from your TF state files.
The IaC Explorer in Firefly employs event-driven backends. Once Firefly scans your IaC stacks, it finds as soon as any updates are made to your cloud infrastructure, significantly reducing the time required to view changes in your IaC status.
