It works well enough for Netflix - https://medium.com/netflix-techblog/edda-learn-the-stories-of-your-cloud-deployments-ade4f4edd9cd https://medium.com/netflix-

It works well enough for Netflix - https://medium.com/netflix-techblog/edda-learn-the-stories-of-your-cloud-deployments-ade4f4edd9cd https://medium.com/netflix-techblog/edda-learn-the-stories-o... - and Target ( https://tech.target.com/2017/04/07/how-and-why-we-moved-to-spinnaker.html https://tech.target.com/2017/04/07/how-and-why-we-moved-to-s... ) :). I've only ever used Edda as part of a Spinnaker setup, but there's no reason it couldn't be used with something else, or the same idea in general reused. You don't have to cache it for very long, but you get two benefits here: Being able to query the data and search through it ways you simply can't do when making an API call to AWS, and having primarily only one system munching through your API throughput limits. If you've got a large account with a lot of resources and a lot of people or systems that are querying the API frequently, you'll probably have more consistently available data, rather than having systems sitting around doing retries and getting throttled there, on repeat.