3 ms·
> As for no recommend approach - that's deliberate. I don't think most people working on Node want a Rails equivalent This is a useful way to understand what N
by dcwca 11y ago
> As for no recommend approach - that's deliberate. I don't think most people working on Node want a Rails equivalent
This is a useful way to understand what Node is. Node's core API is for building any sort of network service: A DNS server, an SMTP server, HTTP server, socket listener, etc. and so it applies to a wide and varied set of problems. Rails is for building a very specific type of database-backed web application.
- pluma 11y agoExactly. I don't think Node is a good fit for monolithic CRUD apps. These are already solved problems in various other languages. Instead Node lets you compose small purpose-built modules.
- techdragon 11y agoNow out only problem is how to build decoupled/distributed micro services. I'd argue only Erlang and Elixir are going to survive into the multi core multi server future, but that would be little more than a slightly educated opinion unless I take the time to write a very large explanation with cited references. I don't have time for that this week.
- vkjv 11y agoWe are an (almost) completely node.js team and are having quite a bit of success using it for microservices. gRPC makes communication fast and easy, while Docker and Kubernetes make deployment and composition just as simple.
- pluma 11y agoPersonally I prefer having a monolithic app at the core and using Node as the glue to tie everything together (e.g. to provide "real-time" features or to integrate third party services). I think what's holding Erlang back is mostly its rather obscure syntax. Only a mother could love that.