20

Mar

Richardson Maturity Model

The Richardson Maturity Model (RMM) is a maturity model suggested by Leonard Richardson to assess the maturity of a API service. In other words, the Richardson Maturity Model can be used to determine how well a Web service architecture adheres to REST principles. It defines the four levels (0–3) based on URI, HTTP verbs, and hypermedia. Each layer builds on top of maturity of the layer below. The higher the API in the level, the more mature it is.


4

Mar

mule 4 connectors debug logging

How to Enable Logging for the different connectors in Mule 4 applications in anypoint studio and cloudhub The following configuration is used to enable verbose logging for debugging purpose. Some important points to note when enabling verbose logging - The application performance is impacted when enabling verbose logging as it has to log each and every thing associated with the particular connector enabled for logging. - Debug/verbose logging should be done only temporarily and only for the duration of troubleshooting. - All logging will be done in plain text so be aware of any sensitive information being logged in cloudhub or logged to external services.


13

Feb

Concurrency vs Multi-threading vs Asynchronous Processing

Simple explanation on Concurrency vs Multi-threading vs Asynchronous Processing There is a common misconception on Multi-threaded, Asynchronous and concurrent processing. Some even think that they are same as their definitions overlap, and they are often used interchangeably. First we need to understand the terms threads, synchronous, Asynchronous, concurrency and multi-threading to understand the concepts. Threads: Without going in depth details on what a thread is lets consider a thread as a worker to do a tasks


9

Feb

Rest API versioning

Change is inevitable and this is no different with APIs. If APIs are successful, they evolve over time. New requirements may drive you to make changes to your APIs. Advancements in technology are also a contributor to changes to APIs. Handling these changes in a way to minimize the impact on the clients is the art of versioning. Versioning is the process of assigning unique version numbers to identify the current changes associated with the product/software. Within a given version number (major, minor), these numbers are assigned in increasing order and correspond to new developments in the software release. Hardware product or a software product, everything is versioned. Without versioning it would be a maintenance nightmare.


7

Feb

Rest API best practices

Designing and building a REST API takes time, takes effort and most importantly takes the right skill. REST APIs should be easy to understand, well documented and follow standards so that integration is straightforward. This can be acheived only if we follow the best practices when designing a RESTful API. Lets look into the REST API best practices to design and build great APIs which are robust and reliable. APIs are a generic concept that can be explained in many ways for example, - An API is a web service which delivers resources via web technologies such as HTTP. - APIs are interfaces used for system to system communications. - APIs are used for building distributed software systems to enable loose coupling.


Subscribe for more goodness!

Do you like what I'm writing? Sign up to receive new content straight into your mailbox!