NoSQL Engineering: MongoDB, Cassandra, Aerospike, DynamoDB & Cosmos DB
NoSQL clusters run quietly until a version leaves support, a partition gets hot or the bill doubles. We upgrade, re-model, migrate and tune MongoDB, Cassandra, Aerospike, DynamoDB and Cosmos DB with the same discipline we bring to relational systems.

Dates that drive this work
- days MongoDB MongoDB 7.0 reaches end of life (Server and Atlas Dedicated).ics
Sources: MongoDB Software Lifecycle Schedules
Sound familiar?
- MongoDB 6.0 is already out of support and 7.0 ends on August 31, 2027; you want to land on 8.0 without surprises.
- Your Cassandra 3.11 ring has been unsupported since September 2024 and the upgrade must go one major version at a time.
- Aerospike 7.x releases reached end of life during 2025 and 2026, and the team that built the cluster has moved on.
- DynamoDB or Cosmos DB costs are climbing because the partition key and access patterns no longer match the product.
What you receive
- Health check report with prioritized findings
- Version path and rolling-upgrade runbook
- Data model recommendations
- Cost and capacity review
- Monitoring, backup and restore tests
What we deliver
Scope is confirmed in writing in the assessment, with anything out of scope listed too.
- 01
MongoDB and Atlas
Rolling replica-set and sharded-cluster upgrades, self-managed to Atlas migrations, index and schema reviews, Atlas cost tuning.
- 02
Cassandra and Astra DB
Rolling 3.x to 4.1 and 5.0 upgrades, repair and compaction strategy, and moves to DataStax Astra DB or managed Cassandra.
- 03
Aerospike
Version upgrades, namespace and storage-engine design, cross-datacenter replication and capacity planning.
- 04
DynamoDB and Cosmos DB
Access-pattern and partition-key design, capacity mode choice, global tables and request-unit cost reviews.
- 05
Data modelling
Documents, wide rows and keys designed for the queries you actually run, with migration scripts.
- 06
Operations
Backups you have restored, monitoring and alerting, and runbooks your team can follow.
Fixed scope and a fixed fee, agreed in writing.
Every engagement is scoped after a free 30-minute review. The scope and fee are confirmed in writing before work starts, and the assessment fee is credited toward the project.
Step 01
NoSQL health check & upgrade plan
Fixed fee, scoped after the free review
Cluster health, data model and hot-spot review, version path, risks and a fixed quote for the work. Credited toward the project.
Step 02
Upgrade, migration or re-model
Fixed fee, scoped after the free review
Scoped per cluster or workload from the health check, agreed in writing before work starts.
Samples and an example engagement
Templates with fictional systems and an illustrative scope, so you can judge the depth before the first call.
Cassandra 3.11 and MongoDB 6.0 off end-of-life versions
A platform team still runs Cassandra 3.11 (end of life since Sep 2024) and MongoDB 6.0 (end of life since Jul 2025) behind customer-facing services.Sample deliverableSample assessment report: database upgrade readiness
The structure and depth of the written plan you receive at the end of a paid assessment, shown with fictional systems.Sample deliverableSample cut-over runbook: PostgreSQL major upgrade with blue/green
A step-by-step runbook excerpt with timings, owners, checks and the rollback path.From first call to delivery
You can stop after any step and keep everything we have written.
- 01
Free
Free 30-minute review
We look at what you run, what is urgent and whether a fixed-fee engagement fits. You get a short written summary.
- 02
1–2 weeks · credited
Health check & plan
Findings, version path and a fixed quote.
- 03
Typically 2–8 weeks
Upgrade or migration
Rolling, rehearsed changes with no big-bang cut-over.
Technologies
Names are trademarks of their owners. Listing does not imply partnership.
Questions about this service
Straight answers on scope, fees and how we work. Anything else, ask us.
Can you upgrade Cassandra without downtime?
Yes, in most cases. Apache Cassandra supports online, rolling upgrades between adjacent major versions. We upgrade node by node with repairs and checks between each step.
Should we move from self-managed MongoDB to Atlas?
Often it pays back in reduced operations work, but not always. The health check compares the run cost and operating effort before you decide.
Do you work with DataStax or MongoDB directly?
We are independent and not a vendor partner. We work with your existing vendor support contracts where you have them.
Is the health check fee credited?
Yes, in full, toward the project if you go ahead.
Start with a free 30-minute review.
Databases, cloud or AI: talk to a senior engineer about what you run and what is coming. We reply within one business day and sign your NDA on request.

