Currently, there are five main methods of fetching data from EVA:
- Web services
- Event exports
- Synchronization files
- Datalake exports
Our web services are straightforward. You know them, you love them, no further explanation necessary.
You don't always want to rely on web services for certain operations. Sometimes you want to act upon certain events, which would require you to constantly check if these events have occurred when using web services. No bueno. For these purposes, we provide event exports. Event exports essentially boil down to us updating you of events as soon as they occur, so you can go do your thing.
This is the recommended method of receiving updates from EVA, as it acts in real-time.
Synchronization files are new, they are awesome, and open up a field of new possibilities. What it essentially allows you to do is to export certain configurations as a json, which can then be used to compare it to a whole different environment or even version control the same environment.
Additionally, if you set up an Azure storage, Amazon S3 or Google Cloud account we can push a shit ton of data over to your data lake. No sweat.
For customers that chose EVA because we are hot, the next big thing or indescribably awesome (which is definitely understandable), but do not care for real-time data or small and nimble traffic (which is nowhere near understandable) we also provide data feeds.
Even though we provide and support data feeds, we have much, much better alternatives for every single one.