API Virtualization and how to fix UI-API expensive integrations across teams in different organizations

Last updated: 4 months ago

The Empire state was completed in 14 months - 12 days ahead of schedule - and it cost 60% of its original budget. Why do large companies go into multi-year development, usually delivering after the original timeline with costs at 150-200-300%?

Medium to large companies running large projects suffer expensive painful UI-API integrations. As we move into distributed micro-services ecosystems, this can get highly expensive pretty soon.

One important factor is human communication complexity when it involved multiple teams across multiple organizations with different goals and consumers, distributed across the world.

Is Swagger working for you today? What are the tools that can help us reduce the friction, unblock and accelerate the dependent teams across the org?

Let's review some of the API Virtualization tools at hand and how to include them on the development flow. In a GraphQL world, apollo mocks or graphql-faker are a good example. Or in a REST world, we could leverage Hoverfly.


4 months

This talk is targeted to both junior and advanced professionals aimed at sparking conversations to improve API integrations flows, focusing on consumer driven contracts or leveraging the tools to overcome classic mental models.

Log in to comment