Azurite vs MockServer

Azurite is a free, open-source server emulator for trying Azure Storage APIs on a local machine. Azurite V3 supports Blob and Queue storage, while Table storage is marked preview. Blob functionality includes containers, block and page blobs, service properties, and CRC-64/NVME transactional checksum checks for specified writes. Queue operations cover creating queues and putting, getting, peeking, updating, deleting, and clearing messages. Documented authentication includes Shared Key, account and service SAS, OAuth, and supported public access. It works with Azure Storage SDKs, Azure CLI, and Storage Explorer. Installation options are npm, Docker, a Visual Studio Code extension, or cloning and building the source. The npm route supports Windows, Linux, and macOS with supported Node.js LTS versions. Local hosts, ports, workspace, and optional in-memory persistence are configurable. Telemetry is enabled by default, with an execution-level disable option. It uses the MIT License.

MockServer is a free, self-hosted tool for mocking and proxying HTTP, HTTPS, and gRPC services during isolated testing. It can verify requests as well as stand in for services. Teams can generate mocks and validate traffic against OpenAPI or Swagger contracts, or import recorded sessions from browser HAR files and Postman collections. Beyond HTTP services, it can mock gRPC, AsyncAPI brokers such as Kafka, MQTT, and AMQP, and OAuth2/OIDC providers. Its protocol coverage includes HTTP/1.1, HTTP/2, HTTPS, SOCKS, and experimental HTTP/3, which uses a separate UDP port. For fault-oriented testing, it can add latency, errors, dropped connections, and malformed responses to mocked or proxied traffic. Deployment options include Docker, an executable JAR, Helm/Kubernetes, Testcontainers, Homebrew, and a JVM-less bundle. A web dashboard displays logs, expectations, and recorded traffic; Prometheus metrics and OpenTelemetry tracing are available for shared environments. Each instance includes an MCP server at /mockserver/mcp. The /mockserver/status and /mockserver/ready probes remain reachable without authentication or authorization.