API Mocking and Proxying

1 post · Mar 2020

What this trail covers

This feature thread tracks the evolution of API mocking and proxying tools to reduce the 'blocked factor' in API-driven development. It covers solutions like Mox, which acts as a hybrid proxy and mocking framework, allowing developers to proxy requests to a live backend while selectively mocking specific endpoints. This approach aims to balance the flexibility of API mocks with the maintainability of using a live backend, reducing developer downtime and improving iteration speed. The thread explores trade-offs between pure mocking and live backends, and discusses various implementation options like webpack-dev-server, MockServer, Interceptor, and GraphQL Faker.

All Confluent trails

Mar 2020The API Dilemma – Choosing a Mock API vs. a Real BackendThis post introduces Mox, a new tool developed by Confluent to address the 'blocked factor' in API-driven development. Mox is a lightweight request interception library that wraps around Express. It acts as a proxy server that can be extended with mocked API endpoints. By default, Mox proxies incoming API requests to your real backend, but allows specification of endpoints to mock or modify. Key features include request introspection, proxying to multiple backends, setting headers and status codes, simulating delays, and generating SSL certificates. The post details the trade-offs between API mocks and live backends, and presents Mox as a hybrid solution that combines the benefits of both.
Advertisement