The choice between SQL and NoSQL backend services is not a matter of right or wrong, but of fit. We believe the decision should be driven by your app's data structure, query needs, and long-term scalability, not by trend or convenience. This guide does well to present both options without hype, and that neutrality is exactly what too many developers skip in favor of dogma.
For most applications with structured data and complex relationships, SQL remains the practical default. Transactions, joins, and enforced schemas still matter, especially when your app handles financial records, user accounts, or inventory systems. If your queries are predictable and your data fits neatly into tables, choosing SQL saves you from reinventing consistency and integrity layers yourself. The guide's emphasis on this point is correct: relational databases are not outdated, they are battle-tested. What this means for you is straightforward. If your team already knows SQL, you can ship faster and debug less, because the tooling and community support are mature.
NoSQL becomes compelling when your app's requirements push past what relational models handle gracefully. Unstructured data, horizontal scaling across distributed systems, and high-velocity writes are genuine use cases. If you are building real-time feeds, IoT ingestion, or content-heavy platforms where schema flexibility matters more than strict consistency, a document store or key-value backend can reduce friction. But the guide rightly warns that NoSQL is not a shortcut for poor data modeling. You trade transaction guarantees for performance and flexibility, and that trade must be intentional. For you, this means asking whether your future growth is better served by scaling out rather than up, and whether your team can manage eventual consistency without tripping over it.
Our plain take is this: do not choose a backend because it is newer or more fashionable. Choose it because it solves a problem you actually have. The guide's neutral comparison is a useful starting point, but the final decision belongs to your app's specific constraints. Run a small prototype with each option, measure real queries, and test failure modes. The backend that fits is the one you can maintain confidently in two years, not the one that impresses in a blog post. Make that call with your data, not your ego.