Client background and business context

  • Client profile: electronics retail company 
  • Project: API-first integration for enhanced availability and reservations of stocks 


For this client, API monitoring checks to see if one or more resources are available (and therefore responding to calls) or not. Receiving notifications about any possible breaks in the chain of dependence allows companies to act appropriately in order to ensure that the main platform stays online even if other connected assets and platforms do not. 

  • Enhance availability for order processing: availability is one of the most requested information during the order taking process. Availability is not a fixed value, but in this case, it needed to be calculated for better predictions and responses to the eventual critical situations. 
  • Connect different touch-points from different locations: create a way in which different locations can provide information in a unitary way. 
  • Create the ability to add new touch-points: as the working locations and the company’s services increased, the system must act accordingly and be able to respond to the new business needs. 
  • Increase system performance: the company’s system should’ve been scalable and able to handle at least 1.000 queries per second. 
  • Time to market: release the system in a short period of time, without affecting the company’s processes and normal data flow. 

Our approach

In a consultative approach, together with the clients we started mapping the requirement and the needs of the existing ecosystem. 

The company had different services, each with a collection of different APIs. Each service describes a specific capability, with well-defined scope and entities. To increase the efficiency of the system, we used a decoupled architecture that allows the company’s users to move, replace services, as well as their underlying persistence systems. 

After thoroughly researching the company’s needs, we have defined the APIs needed, together with their methods, restrictions, and pre-conditions. To ensure the correctitude of the implementation, we set up API blueprint testing, as well as API automation tests. These tests were done while building logic downstream. Our teams managed to enable in parallel different systems which were ready for requests, in a record time. 

The company has different touch-points in different locations. As the company is in continuous growth and diversification, together with our clients we have decided to create a future-ready solution that would address all the business requirements. We focused on defining the services in a microservices platform. In parallel, we ensured the integration of different touch-points, as well as the creation of new touch-points. 

Technologies used in this case study


  • MongoDB
  • Apache Tomcat
  • Docker
  • Java
  • Spring by Pivotal
  • Gradle
  • Git
  • Kafka

Related case studies

Performance testing for continuous volume testing

Implementing and documenting a long-term, sustainable appr ...

API first integration for enhanced availability and reserv ...

Receiving notifications about any possible breaks in the ...

OMS integration for increased speed, consistency, and qual ...

Undergoing the rollout of an integrated OMS, requires comp ...

Say hello


Eschborner Landstr. 42-50
60489 Frankfurt, Germany
Phone: +49 89 2154 851 15


Walter-Gropius-Str. 17
80807 Munich, Germany
Phone: +49 89 2154 851 15


Wallisellen, Zwirnereistr. 22
8304 Zürich, Switzerland
Phone: +41 44 830 92 30


Constanta 12, Platinia
400158 Cluj-Napoca, Romania
Phone: +40 364 115 115


Cetatii Square 1, Oradea Plaza
410520 Oradea, Romania
Phone: +40 364 115 115

Whether you’re interested in our services or you would like to learn more about our company, we are happy to provide you with the information you need.