Azurite vs Microcks

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.

Microcks is an open-source tool for mocking and testing APIs and microservices. It works with OpenAPI, AsyncAPI, gRPC/Protobuf, GraphQL schemas, and SOAP, and can build mock responses from examples, generate realistic data, or alter mock data and responses dynamically. It also checks provider and consumer contracts against live implementations and specification versions, and automates checks in CI/CD pipelines with integrations for GitHub Actions, Jenkins, GitLab CI, and Tekton. Containerized deployment supports on-premises, cloud, and developer-laptop use; its Uber distribution is intended for laptop work and unit tests, using ephemeral in-memory MongoDB. The free, community marketplace for API mocks and test suites is enabled by default. Microcks is a CNCF incubating project, with a listed price of free. The public demo is read-only and cannot import APIs or change artifacts. Documentation cautions against production use of the all-managed Kubernetes setup because its single Keycloak and MongoDB instances are not tuned for scalability or security best practices.