From DynamoDB to Bunny Database
A multi-agent operations platform that audits, hardens, prioritizes, and tracks work across the rest of the portfolio. Back Office is built around transparent automation, operator control, and privacy-first hardening instead of surveillance-heavy workflow tooling.
Common questions
Why leave DynamoDB if it scaled well?
It scaled well but it added operational weight that did not match the portfolio. The single-table design patterns, capacity planning, IAM policies, and SDK ceremony were more infrastructure than these workloads needed.
What is Bunny Database?
A database service on Bunny's platform. It lives on the same infrastructure as Magic Containers and Bunny Storage, so the data layer and runtime are colocated without crossing provider boundaries.
Did the data model change during migration?
Yes. DynamoDB's single-table design forced everything into partition key and sort key patterns. On Bunny Database I could use a more natural relational shape where it made sense, which simplified queries and reduced the number of access pattern tricks.
What about backups and durability?
Bunny handles replication and persistence. For critical data I also keep periodic exports as a safety net, the same way I would with any managed database.