At the start of every new year, us web developers usually have a few questions on our minds, one of which is “What’s going to disrupt the industry this year?”. It could be a programming language that picks up some steam and rises to the top (like AngularJS in 2018 - all of us React devs are crying inside.) Or it could be a faux-winner (like BlockChain technology - more on this later.)
Welcome to Part 2 of Effectively Using Caching While Developing APIs in Mule!
There are multiple approaches that can be used in mule to implement caching for APIs, based on what data you decide to cache.
The two prominent approaches are:
The importance of corporate citizenship has long been emphasized at Appnovation since our global partnership with WE Charity in 2015. This past year has been filled with many exciting community initiatives both at the local and global scale.
Locally, offices have taken the time to get involved with charities and organizations impactful to them.
Push Notifications allow for the delivery of targeted information from an app to a mobile device or desktop computer without a specific request from the app. This means the app doesn’t have to be opened for the content to be delivered directly to the lock screen of the mobile device, or to the notification dashboard.
Caching is one of the most effective design strategies for improving the latency and performance of an API. An API taking a longer time to respond may result in cascaded delays and timeouts in the consuming applications. Further, a longer processing time of an API could result in consuming and blocking more and more server resources during high volume API calls and may end up in server crash or deadlocks.
Drupal Tip: Using $form['#after_build']
Mule MUnit - Tips for Writing Unit Tests
Quick Tip(s): Using CSS to hide button text