The BBVA API Market team tells you what's behind an API
If you want to know how APIs work, it may be very helpful to know all the architecture behind it, its components, its advantages and all the organization of the work. The team of BBVA API Market developers explains all the details in this interview.
Talking to the BBVA API Market development team is an opportunity to enter the world of APIs differently and know their way of working at the technical level. Daniel Gaitero, software architect at BBVA, explains what the architecture behind an API is like. He tells how after considering several options, the team decided to opt for microservices architecture by using Spring Cloud and Docker containers.
For Thomas Person, also a software architect at BBVA, using this architecture has greatly facilitated the team's work, especially through the flexibility which it enables. Something that would not have been possible with a monolithic architecture. The system is simple: when a developer uploads a change to a repository, this code is downloaded, compiled, tested and packaged. All automatically. Then that package is uploaded to a record and deployed to different environments from there.
Jesús Barquín, another of the team's software architects, stresses the automatic nature of the process, which is undoubtedly a fundamental requirement. Moreover, within that automation process, there are also two distinct testing phases: "In the first phase we run, after compiling services, unit tests and integration tests that test our service isolated from other components of the architecture. Once these tests have been successfully completed and the container has been created, it is deployed in our development environment and then moved on another testing phase designed by our QA team."
Sign up to the BBVAOPEN4U newsletter and receive tips, tools and the most innovative events directly in your inbox.