After a thorough evaluation, an Insurtech startup has selected Traffic Parrot's service virtualization and API mocking tool in April 2019 for their application development needs. In this case study, we will look at the details of their infrastructure, how they applied Traffic Parrot, and what issues they have come across.
Traffic Parrot is specifically designed to maximize the productivity of developers writing automated tests and to enable them to mock out microservices for local development. Their lightweight platform with gRPC support was a good fit for our Docker and Go-based development environment. They provided strong support during the POC and continue to track the rapid evolution of gRPC, acting as an effective extension to our team.
The colocated teams developing a microservice to encourage close communication. gRPC APIs connect microservices, which are sometimes owned by different teams. Developers design gRPC APIs using Proto files, which form the contract between microservices.
Starting more than a year ago, the company developed multiple microservices in parallel. For example, the Policy Administration team provided gRPC APIs for the Enrollment team to consume. This meant that developers on the Enrollment team were sometimes waiting for the Policy Administration team to deliver their microservice APIs before they could start working.
This led to blocked timelines between teams, which meant the company could not deliver at the fast pace required for their customers. It was urgent for the company to find a solution to allow the teams to work independently.
Traffic Parrot was identified as a candidate for a gRPC API mocking solution that could help unblock the timelines between the teams. After a two week technical evaluation by VP of Engineering, it was clear that the open-source alternatives did not provide adequate capabilities and Traffic Parrot was chosen to fulfil the company's development needs.
Teams use Traffic Parrot to develop both sides of their gRPC APIs in parallel, without having to wait for the server code to be written before a client can be tested. They run automated test suites on their CI build agents, with Traffic Parrot running in a Docker container on the agent.