DynamoDB Local vs Hoverfly

DynamoDB Local lets developers develop and test applications without accessing the DynamoDB web service. It can run without an internet connection, and AWS says local use can help avoid throughput, storage and data-transfer fees. Developers can obtain it as a download, Apache Maven dependency or Docker image, and AWS documents use with the AWS CLI, AWS SDKs, Docker Compose, Maven and AWS CloudShell. Data can persist in a local database file or remain in memory, where it is lost when DynamoDB Local stops. The downloadable version requires configured credentials, though AWS says they need not be valid AWS credentials for local access. AWS identifies v3.x as current and recommends it for local testing and development; v2.x is legacy and v1.x is deprecated. Running v2.6.0 or later requires JRE 17.x or newer. Telemetry can be disabled with a command-line option or environment settings. DynamoDB Local does not support point-in-time recovery, tagging or vector indexes; it also lacks parallel scans, ignores provisioned throughput settings and treats table names as case insensitive. AWS describes it as a development and testing tool, not a production service.

Hoverfly Cloud is a hosted API simulation and mocking platform for testing without live API dependencies. It handles HTTP/S services including REST, SOAP, XML, JSON, and GraphQL. Users can capture and replay traffic, generate simulations from OpenAPI specifications, and match requests by methods, headers, parameters, and bodies. Simulations can delay responses, inject faults or errors, and modify replies. A command-line interface supports scripted configuration and testing pipelines. Hoverfly and hoverctl binaries run on macOS, Linux, and Windows, while documentation covers Docker and Kubernetes installation. The underlying Hoverfly framework is open source under Apache 2, has no GUI, and is generally run locally or in a user’s infrastructure. Cloud use cases include performance testing, functional testing, and development.