API Streaming: Cache And Push Data From APIs Using StreamData.io
I was introduced to StreamData.io the other day, by Gabriel Dillon (@gjdillon) of Readme.io. StreamData.io provides a caching, and push layer for apps to take advantage of, that can be deploy on top of existing APIs. I haven’t implemented StreamData.io yet, I am still evaluating it, and at first glance it looks like an interesting new real-time layer, that you can use on top of APIs, to improve application performance and user experience.
I’m going to add StreamData.io to my real-time research right now, however once I start playing with I may add as an API deployment resource as well. I have some verification to do, but I’d love to test out the potential for StreamData.io to deliver cache and sync layer for common APIs, doing for APIs, what StreamData.io is doing for apps—delivering on one of my ongoing ideas for caching high use APIs.
When I was working in Washington DC, I had the pleasure of working during the federal government shutdown, where I wrote a piece asking if we can depend on our federal government APIs, and talked about caching APIs with AWS cloud formations, or Open Shift. My objective is to ensure there redundant sources for APIs coming out of government, providing developers with a more stable solution, they can depend on. I even added this thinking into the early APIs.json design, allowing you to define cached indexes of APIs.
I’ve added StreamData.io to my real-time research, and I’ll get in there and play with more, as I have the time. Then I’ll get a better understanding of what you can do with the API caching and syncing, seeing if it is possible to deliver this layer for my APIs as well as my apps—something that is even more appealing in this age of Docker containers. #FoodForThought