I'd like to post yet another presentation surrounding API Management. This time I've focused on using a cache as a method to reduce your response time for your APIs and improve speed and performance resulting in a much better user experience for your developers!
Knowing why and when to use a cache is exceedingly important should you choose to go this route. Misuse of caching technology in order to replace a data-store or over cache can actually hinder performance and result in unintended consequences such as loss of data. Proper use however can result in wonderful speed increases and drastically reduced loads on your services.
This presentation covers the hows and why of using a cache, some of my favorite technologies for caching, and some performance considerations when caching. It's important to look at a variety of aspects when considering a cache such as frequency of use of resources, database performance and load, and redundant calls for similar or same information. By careful consideration of these factors, you can make your APIs faster, better, and truly make your developers happier!
Note: This content will be presented at various API meet ups around the east coast and has been generated in my role as a CA APIM Principal Consultant. The topic of caching, performance, and speed in APIs is one I consider CA Technologies to be highly knowledgable on and they provide a very comprehensive set of DevOps and API Management solutions. Feel free to reach out to either myself or any of us at CA to talk about how you can better secure your APIs.