Azurite vs Wilma

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.

Wilma is free, GPLv3-or-later software for developing and testing applications that depend on other services. It combines a service stub with an HTTP/HTTPS transparent proxy, allowing teams to capture, decode, save, and forward traffic, including two-way SSL, or generate configured responses. It can operate as a proxy, a stub, or both. JSON files define stub behavior, and configurations can be uploaded or changed through the interface or service while Wilma runs. Real-time interceptors can inspect or modify requests and responses; custom interceptors, condition checkers, and response formatters can be added, including through classes or JAR files. Message Search finds logged request-response pairs. Wilma supports unit, integration, functional, end-to-end, performance, and manual testing. It is available as Docker images, GitHub release ZIP files, or source builds. The application requires JRE 11, while Message Search requires JDK 11. Logging can be controlled and old logs deleted on schedules.