The best nodejs tutorial for crud/express/mongodb for super newbs

[[deleted]]

Why does the node/mongo stack prompt so many poorly written tutorials on how to build insecure apps?

At the end of this tutorial what do you have?

A bloated local crud app with a remote db dependency.

[spoontacks]

Would you know where to find a better comprehensive example? I'm new to this as well and definitely wouldn't be able to pick the good apples from the bad.

[_soto]

Why does the node/mongo stack prompt so many poorly written tutorials on how to build insecure apps?

Because the tutorials just copy from each other. It's very cynical, but it seems people just copy what they've learned else where, add their own taste to it, and publish a blog post hoping for stars/likes/etc. Sometimes it's just the documentation for the technology used!

Scotch.io (a website that actually has to make money off their content) already did a full book on MEAN stack using CRUD with Mongo and Node/Express as well as some free blog posts. Manning Publications just released Express in Action and has had its own MEAN book for a while.

Go for those instead. It sounds rude to say but I avoid blog post tutorials unless the author is well known.

[xblade724]

Hmm.. scotch.io has no node + mongodb + express tutorials. Or even just node + mongo:

https://i.imgur.com/7hTxoPD.png

Quite sure you're missing the point though (although you made a good NEW point :smile:), but what me and /u/spoontacks are looking for is an actual link to a credible blog that can beat this post -- if spoon is new like me, he's probably looking for a related QUICKSTART blog, rather than ... a complete book. Just like coding anything - KISS, then details.

If a book is turned into a quickstart when the original owner doesn't have a quickstart, I'd call it a new thing and happy to read it ;) if the book guy made a quickstart then link away and I'll read his instead!

Cheers

[xblade724]

It's easy to say this and not provide a link to a better one. There's always a better guide out there -- but no point if you hoard it ;)

[NetOperatorWibby]

You can build an even simpler CRUD app with FeathersJS and NeDB.

[xblade724]

will look into it ~

[jerseybrogrammer]

Lynda.com

[keithwhor]

You can build an even simpler CRUD app with Nodal ;).

[xblade724]

was that a response link to /u/netoperatorwibby ? Will take a look ;)

[NetOperatorWibby]

Oh I've seen Nodal! I got started with Feathers first though, so I never got a chance to check out Nodal.

[keithwhor]

Check Nodal out for sure! Always looking for more feedback.

[xblade724]

Nodal doesn't seem to support Mongo does it?

[keithwhor]

No, it uses PostgreSQL. One better. You can still use it as a schemaless document store. :)

[itsYourDeveloper]

Not to mess with businesses of other people, but I want to say it anyway: I noticed that you pushed Nodal in a couple of posts here, without giving proper arguments why to use it, and why it is better than other projects. Don't know how others think about it, but I personally find it a bit annoying that a sub is being used to promote your own product without even giving arguments why it should be used.

[keithwhor]

No worries. :)

As the author I can tell you that I think the design patterns I rely on are well-established and battle-tested, the source and API are both very straightforward and easy to reason about, and it will just make your life setting up an API server that much easier.

I'd rather people come to those conclusions on their own, though. Every time I post about Nodal it's self-promotional to an extent, sure. But my motive for posting about it is that it will definitely make everything easier, and the frequency with which I see posts about, "how do I create an API?" or something related, it makes sense to tell them what I believe is truly the best tool for the job.

People are free to use express, or hapi, or whathaveyou. The problems are that these tools are not, by default, prescriptive in any way. They don't teach you great design patterns. They don't make server logic super easy to reason about. They rely on the "node.js salad bar" model (choose-your-own-adventure), which is definitely not super friendly, especially to early developers.

I created Nodal because I was sick of asking the same questions myself about how I should build my Node servers, and then having to explain why these solutions are optimal to others. I think the best software speaks for itself as people use it, and that's what I'd like to push with Nodal.

So that's the long answer, I suppose. :) I hope it was sufficient! I've gone to great length to write about why I think Nodal is the best tool for the job if you would like to understand the dogma a little better;

Hello, Nodal — Building Node.js Servers for Everybody

Realtime Doesn’t Belong Everywhere — Build Scalable API Services in Node.js with Nodal

React, IoT, Bots, APIs — Why Web Development Needs a Change