We will see what to have in component tests for an event-driven microservice and understand what component testing is and how it's different from unit testing.
It sounds like a task, but this video will take you through the entire process of integrating Spring 4, Hibernate 4, MySQL 8, and Maven in around 10 minutes.
This article explores key fundamentals of API design — from language, error handling, and versioning to simplicity and consistency in data representation.
Object Store Connector is a Mule component that allows the storage of key-value. It stores data in the form of Key-Value pair and provides 7 types of operation.
As systems are evolving and the wide adoption of microservices, the number of dependencies for a given microservice is ever-increasing, thus impacting the overall SLA.
Many libraries use Redis for distributed locking, but some of these good libraries haven't considered all of the pitfalls that may arise in a distributed environment.
Hello Muleys, Here's another interesting article on how to restrict additional queryParams and headers that are sent other than those defined in RAML. We all do the test if the required parameters are working fine or not but we forget to test if unnecessary parameters sent along with required parameters. What happens if unwanted parameters are sent? There are chances that attackers might send some thousands of queryParams and Headers with large content. In that case, your application will crash. So what to do? Here's the solution: I have designed a basic RAML with the below resource : When you download the RAML and generate flows, There's an option to restrict additional parameters or headers in APIkit Router Module configuration : By default the configuration is disabled. You have to enable the strict validation config as below: Now your application will not be allowed to pass additional fields: Removing unnecessary fields will give a successful response: Check out this video for the live demo:
All APIs developed using Mule must be built with a health check endpoint. This template will help you maintain a uniform structure across all the APIs and their layers.
A DevOps toolchain is a collection of tools that operate as an integrated unit to design, build, test, manage, measure, and operate software and systems.
I describe how I created the API definition, then how I created the server and client code from the API definition. Then I will talk about some of the problems I faced.
CORE
