At some point, you may have a service that returns a lot of fields and related objects. What if the service consumer doesn’t want all the fields all the time? In other words, he/she would like to have the response
I guess that we more often think about our services in “happy path” term, but we underestimate not so happy paths. What if my API is trying to reach another API/system and it is failing constantly? Can I reach it less often in case of timeout? I thought about that in case of a Mule 4 application and I come up with Circuit Breaker pattern. In this article I will briefly introduce the pattern and show you how you use it in your Mule application.
Lately, I had to design the solution that would store errors next to the application on CloudHub in Object Store v2. However, the problem arouses when the object store started to contain more than one thousand entries. Eventually, the solution
In the previous article I have described how to share common functionality encapsulated in flows and subflows. This time I will focus on common configuration that should be shared among our applications. Mule has offered domain application that can solve
I found it crucial to be able to share some logic, encapsulated within (private) flow or subflow. In Mule ESB we have a couple of ways to handle that scenario. I will focus on custom maven project. You will see
Content Enricher is definitely an useful integration pattern. It allows easily enrich message content with new data gathered from external resource. In vast majority of Mule’s apps I have been using Message Enricher Component. Today I will point main differences
It is a good practice to monitor your service and check whether it is available and/or is performing as expected. In order to do this, we need to specify what service’s health term means. In this article, I will present two
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.
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.
I have deiced to share basic idea about REST service design. During this blog series I will focus on commonly used HTTP verbs and their usage. However more sophisticated will be mentioned as well. In each article I will present concept with practical examples. To design a service I will use RAML and Open API specifications. Where this would be possible I will also prepare appropriate mule service’s implementation.