All the tutorials and books for node.js seem to use Mongo as the database.  I am not sold on 'document' databases and would like to know how difficult it is to use any version for plain old tried-and-true SQL with Node.js.

Does anybody have any experience in this area?

Views: 259

Reply to This

Replies to This Discussion

One of the traditional knocks on JS is the volatility of doing sql queries from a interpreted script. Not to mention security. In other words, how do you regulate resource for results in a varying client environment. Node.js is supposed to provide a server side capability. However I would be skeptical of it its implementation of a transnational capability. A memento pattern, or ability to rollback transactions, at least until thoroughly tested. Given the fact that most discussions are coupled with no-sql db's is a clue as to what its intended usage should be. Perhaps caches for local search tools like solr. Easy to update, and rebuild, but less likely to be an efficient engine for individualized rdbms queries.

Reply to Discussion

RSS

Happy 10th year, JCertif!

Notes

Welcome to Codetown!

Codetown is a social network. It's got blogs, forums, groups, personal pages and more! You might think of Codetown as a funky camper van with lots of compartments for your stuff and a great multimedia system, too! Best of all, Codetown has room for all of your friends.

When you create a profile for yourself you get a personal page automatically. That's where you can be creative and do your own thing. People who want to get to know you will click on your name or picture and…
Continue

Created by Michael Levin Dec 18, 2008 at 6:56pm. Last updated by Michael Levin May 4, 2018.

Looking for Jobs or Staff?

Check out the Codetown Jobs group.

 

Enjoy the site? Support Codetown with your donation.



InfoQ Reading List

QCon London 2026: From DVDs to Global Streaming How Netflix’s Commerce Architecture Actually Evolved

Dynamic principal engineer at Netflix, Kasia Trapszo, expertly navigates the evolution of the company’s commerce architecture from a DVD rental service to a global streaming giant. Her insights on pragmatic adaptations to billing systems reveal invaluable lessons on agility, localization, and the complexity of modern payment landscapes.

By Daniel Curtis

QCon London 2026: Reliable Retrieval for Production AI Systems

At QCon London 2026, Lan Chu, AI Tech Lead at Rabobank, shared lessons from deploying a production AI search system used internally by more than 300 users across 10,000 documents. Her experience shows that most failures in RAG systems stem from indexing and retrieval, rather than the language model itself.

By Daniel Dominguez

QCon London 2026: Shipping Constantly with Humans and Beyond at Monzo

At QCon London 2026, Suhail Patel, a principal engineer at Monzo who leads the bank’s platform group, described how the bank has built a developer platform capable of shipping hundreds of changes to production every day.

By Matt Saunders

QCon London 2026: Managing Asynchronous APIs at Scale

At QCon London 2026, Ian Cooper, senior principal engineer at Just Eat Takeaway, discussed managing asynchronous APIs in production, showing how endpoint definitions can drive code generation, schema registration, and the automation of messaging infrastructure.

By Renato Losio

QCon London 2026: Your Multi-Cloud Strategy Is a Product Problem — Treat It Like One

JP Morgan Chase engineers Luis Albinati and Surabhi Mahajan argued that multi-cloud complexity can't be solved with engineering alone. Speaking at QCon London, they showed how treating multi-cloud as a product with capability mapping, demand governance, and defined users tames the chaos.

By Steef-Jan Wiggers

© 2026   Created by Michael Levin.   Powered by

Badges  |  Report an Issue  |  Terms of Service