RTS Questionnaire · Question 10 of 52 · file: answers/q10.html
Have you worked with NoSQL databases such as MongoDB, Cassandra, or similar technologies? How many years of experience do you have?
NoSQLMongoDBDatabases
✅ Yes — NoSQL is part of my standard data toolkit, with 8+ years of practical, production-oriented experience.
🧪 Interactive proof: this answer has its own page with a live NoSQL modelling workflow, the code and schema behind it and the acceptance criteria — open the Q10 NoSQL proof →
Technical detail
- 🍃 MongoDB — document modelling (embedding vs. referencing), compound and text indexes, aggregation pipelines, atomic operators, replica sets, TTL indexes and sample-data tooling in .NET/Node.JS projects.
- 🟨 Amazon DynamoDB — single-table design, partition/sort key strategy, GSIs/LSIs, on-demand vs. provisioned capacity, DynamoDB Streams for event propagation and conditional writes for idempotency.
- 🟧 Amazon DocumentDB, Neptune and Keyspaces (Apache Cassandra API) — document, graph and wide-column workloads: node/edge modelling for relationship graphs, and Cassandra-style partition-key design with tunable consistency for high-write workloads.
- 🧩 Other stores — Redis key/value and cache structures, time-series/analytics stores and search clusters in data-heavy platforms.
🧠 How I choose: access patterns first, then key design, then consistency model. I explicitly plan for hot partitions, eventual consistency in read paths, idempotent writes, and the denormalisation that NoSQL requires — and I keep a relational core when strong transactional guarantees are the real requirement.
📈 Cumulatively I have used NoSQL technologies for more than 8 years, and I combine them with SQL platforms (polyglot persistence) behind repository abstractions so the domain stays clean and testable.