Luram Archanjo

I have been working directly with software development for five years using Java and Kotlin language, open source frameworks and tools, with excellent experience in the execution of projects, from obtaining requirements until the implementation in production. I participated in the most varied sizes of projects, from small projects for internal uses to large and global projects, involving clients like Google and Edenred. Solid experience in developing reactive microservices and cloud applications using Java and Kotlin language with the frameworks and concepts such as: Spring Stack, Vert.x, gRPC, Openshift, Kubernetes, Docker, Prometheus, AWS, JMS, AMQP, ORM, REST, DDD and CDI.

Follow me on GitHub


Hi, how are you? I hope everything is fine!

Today I would like to talk about integration and mock. In the last few years, the way that we build software is changing constantly and one way to start a new project is by using the API-first approach.

Summarizing, An API-first approach means that for any given development project, your APIs are treated as “first-class citizens.” That everything about a project revolves around the idea that the end product will be consumed by mobile devices, and that APIs will be consumed by client applications.

So as your APIs are treated as “first-class citizens”, your first task as architecture is to define and provide them as soon as possible. But Luram, my backend it is not ready.

That is the main advantage related to the API-first approach, you enable parallel development and to do it, you need to mock your APIs and when your backend is ready, it is time to turn off the mock and start the integration-test phase.

That sounds a good idea, right?

Yes, it is a good idea, but sometimes the API has many flows and became very complex to mock and maintain it.

On my previous project, I had this scenery so I had thought, I need to keep it simple to maintain and evolve. Then I have found the MockServer project.

What is MockServer?

Mockserver is an open-source project that enables easy mocking of any system you integrate with via HTTP or HTTPS with clients written in Java, JavaScript, and Ruby. MockServer also includes a proxy that introspects all proxied traffic including encrypted SSL traffic and supports Port Forwarding, Web Proxying , etc.

Why use MockServer

MockServer allows you to mock any server or service via HTTP or HTTPS, such as a REST or RPC service.

Getting Started

Well, We have seen all the required concepts, so it is time to get your hands dirty.

Start MockServer

To do that, first, we need to run the Mockserver, there are many ways , but today, we are going to use Docker, so run the command bellow

docker run --rm --net=host mockserver/mockserver -serverPort 1080 -logLevel INFO

After start MockServer, it is time to learn what is Expectations


Expectations are a mechanism by which we mock the request from a client and the resulting response from MockServer.

So let’s create owner expectation, to do that we need to run the command bellow;

            "application/json; charset=utf-8"
      "statusCode": 200,
      "body": {
      	"status" : "UP"

In the example above we mocked a health check API at the address http:\\mocokserver-host:mockserver-port/super-app/v1/actuator/health

So let’s test it, to do that run the command bellow:

curl --location --request GET 'http:\\mocokserver-host:mockserver-port/super-app/v1/actuator/health'

More content

This article is just a concept about MockServer, to learn more, follow this links:

Request Matchers - Method

Request Matchers - Path

Request Matchers - Query String

Request Matchers - Headers

Request Matchers - Cookies

Request Matchers - Body

Creating Expectations

Verifying Requests

Persisting Expectations

Be Happy