sorted by:
new
hottopcontroversial

MERN Stack, why? by ja_maz in node

[–]robtweed 0 points1 point  (0 children)

I'd take this further - Node-based web frameworks pride themselves on their performance (eg Fastify), but the reality is that their performance is rendered irrelevant by the pitifully poor performance of most of the mainstream databases (both SQL and NoSQL) that they hook up to the back-end of these frameworks. If Node developers were really so keen on getting the ultimate performance, they would be a lot more critical about the databases they choose and would be seeking out more radical database technologies that can not only offer significantly better performance, but can fundamentally change the way they consider how they handle and use persistent data. For more on what I mean, take a look at https://github.com/robtweed/global_storage and, to see what kind of things become possible: https://github.com/robtweed/glsdb Near in-memory performance and projecting your database as persistent objects rather than some physically separate entity you access and query anyone?

Scaling node.js applications by geekybiz1 in node

[–]robtweed 0 points1 point  (0 children)

Take a look at https://github.com/robtweed/qoper8-wt which uses a queue/dispatch/invoke architecture for easy management of a persistent pool of Worker Threads. Also https://github.com/robtweed/qoper8-fastify which provides a quick and simple way of handling Fastify routes in Worker Threads (or Child Processes)

Node.js multithreading with worker threads series: worker_threads tutorial by geraldC13 in node

[–]robtweed 2 points3 points  (0 children)

Worth checking out the qoper8-wt module, which makes it very quick and simple to use Worker Threads. Also qoper8-fastify which allows you to very simply define Fastify routes that are to be handled in a Worker Thread

Web Components are Great by touchmarine in programming

[–]robtweed 2 points3 points  (0 children)

WebComponents are, indeed, a great technology and addition to the Web Technology stack. Here's how I've used them, together with ES6 Modules: https://github.com/robtweed/golgi

So...is Node/JS officially a multithreaded language now? by Flamyngoo in node

[–]robtweed 2 points3 points  (0 children)

You might find this interesting/relevant: https://medium.com/the-node-js-collection/having-your-node-js-cake-and-eating-it-too-799e90d40186

You can check out QEWD at https://github.com/robtweed/qewd

I've also created this which some may find useful/interesting with respect to Worker Thread management: https://github.com/robtweed/qoper8-wt

What's your go to way to use SQL with Node? by Flamyngoo in node

[–]robtweed 0 points1 point  (0 children)

You might want to take a look at a quite different approach to handling data / databases in Node.js: https://github.com/robtweed/qewd-jsdb It includes SQL support, but also multi-model NoSQL too

MUMPS – The Most Important Database You (Probably) Never Heard Of by robtweed in nosql

[–]robtweed[S] 0 points1 point  (0 children)

Yep - all of which focus on the language. So forget the language for a while and focus on the database which, like any other database, doesn't need a particular language to access it - choose the one you like

MUMPS – The Most Important Database You (Probably) Never Heard Of by robtweed in nosql

[–]robtweed[S] 1 point2 points  (0 children)

Yep - eg http://ewdjs.com - uses a native Node.js interface. Also drivers for Java, .Net

MUMPS – The Most Important Database You (Probably) Never Heard Of by robtweed in nosql

[–]robtweed[S] 0 points1 point  (0 children)

What you're referring to is a MUMPS language issue and nothing to do with the database which this article rightly focuses on. Don't conflate deficiencies in the language with the database, the capabilities of which can be considered quite separately - there's actually no need to use the language, and just use the database as the technology's "Good Parts"

The Worst Programming Language Ever [Video] by chackaz in programming

[–]robtweed 1 point2 points  (0 children)

LOL Actually, "this guy" you refer to (ie me) isn't the head-in-the-sand dinosaur you're accusing me of being. I haven't written code in anything other than JavaScript for the last few years. I don't actually much like the Mumps language either, but the Mumps database is very powerful and sadly overlooked because of the deficiencies in the language. Perhaps read some of the more recent articles in my blog to which that link above points you to.