Problem and Solution Overview
In our initial meeting, we realized that the project was closely related to the Serverless concept, and that's precisely the path we took and presented as a solution.
At that time, Dock faced the challenge of building APIs from scratch, which would be accessed by their clients (other companies) providing financial services to end consumers, either individuals or businesses. As the number of companies contracting Dock increased, the number of end consumers served on the front end and consuming platform API services multiplied rapidly. This directly impacted the volume of transactions that needed to be supported by this system, which was not initially anticipated.
In the early discussions, we heard keywords like "scalability," "low cost," "REST API," "integration with partners," and many others. The idea took shape, and after extensive studies and hours of work, we had a solution design that looked something like this:
Seeing that even with over 1 million calls in an hour, the response time doesn't increase. In fact, in this case, it even decreased, averaging 350ms per execution. For us, it's impossible to see a result like this and not be proud of what we have created so far.