For high-workload application it is important to manage resources efficiently. One of the tricks that can save resource usage is caching. In RESTful services this technic is used in GET methods. However it may by used in other cases when operation of getting particular resource can be reused. In this blog post I will extend previously design rest service by adding caching to two operations. Mule uses Cache Scope component. Apart from describing it I will show you possible obstacles and how to handle them.
Mule 4.x
Simple GET operations Design Center vs APIKit
HTTP GET method’s simple design has been published in previous article. We designed account service using RAML and Open API specifications. It is time, now, to implement that service so our potential users could consume it. To implement the service I use new Mule’s Design Center available on Anypoint Platform. To follow my steps you would not need to download any software on your PC at all. All will be done within web browser. On the other hand Anypoint Studio is the main IDE to design Mule’s services so I will not omit this tool. Within it I show the possibilities of APIkit message processor.
GET an HTTP method for retrieving resources
This article is an intro into a blog series about HTTP methods usage in RESTful services. As a GET is the most common I will start with it. This method is used for retrieving collection of resources or a single resource. In other words this could be used for searching purposes. However the more advanced search criteria I will describe in next article.
To design a service I will use two most commonly used specifications such as RAML and OpenAPI.