---
title: "Comment by Daniel Collins on \"Choosing a Database Without Guessing\" | Hashnode"
description: "This is a really useful framework, especially the first step. Too many database choices start with the technology rather than the workload, and that is where pr"
url: "https://hashnode.com/posts/choosing-a-database-without-guessing/6af51e466b4efeb139c1f0c5/comment/6af555b76beb14f8fe423359"
---

[Discussion](https://hashnode.com/posts/choosing-a-database-without-guessing/6af51e466b4efeb139c1f0c5)

Comment [Choosing a Database Without Guessing](https://hashnode.com/posts/choosing-a-database-without-guessing/6af51e466b4efeb139c1f0c5)

[Daniel Collins](https://hashnode.com/@fabbalancecheckuae)

[1h ago](https://hashnode.com/posts/choosing-a-database-without-guessing/6af51e466b4efeb139c1f0c5/comment/6af555b76beb14f8fe423359)

This is a really useful framework, especially the first step. Too many database choices start with the technology rather than the workload, and that is where projects get into trouble later. Writing down the real query patterns, data volume, and constraints such as compliance or caching limits makes the trade-offs much clearer. I also liked the point about simulating at production volume before committing — a trial that only uses small test data can hide the exact problems that appear later. The zero-downtime cutover approach is a good reminder that migration planning matters just as much as the choice itself.