This is exactly, what I wanted the frontend developers to do. Junior developers introduce new library/framework just because it looks "cool to work with", later it becomes a problem, which will then be replaced by another library (its a endless loop these days).

Does hasura supports database replication? When I looked last time, it wasn't. Also I feel these tools are not enterprise ready, IMHO.

(I'm from Hasura)

Hasura connects to a read replicas and manages connection pooling across the database cluster.

Hasura itself is stateless so it doesn't do the database replication.

Thanks for the reply. Also, when I run in an microservice architecture, how does hasura handles say for example websocket across the services? Do we need to depend on any other library?

Can you share some samples for these things if available. I will be glad to look at it.

That works automatically!

1. During the lifetime of a websocket connection, bytes should be routed to the same Hasura instance. This most service routers / load balancers should take care of automatically.

2. Subsequent connections from different clients to Hasura need not go to the same instance! This makes horizontal scaling painless.

(Is this what you meant?)

This is great. I did the same for Express.js last year. If anyone interested in it, here is the link: https://github.com/antsmartian/lets-build-express

This is so true that I can relate this myself and my co-workers. We work on javascript side most of the time and daily there will be set of developers talking about new bundlers, react features, hooks etc and they plan to use it in the production. The one thing I see and relate to this article is that, few team have used flow stating its a great tool for static typing in js world and now they are forced to change now to typescript. The same developers who introduced flow into the codebase, now in a position to say flow has huge drawbacks compared to typescript. Now they are moving to typescript, but who knows, typescript can change too. We never know. I always fight against these tech updates, without understanding its cost, but in most cases I fail to.

Not working here in India as well.

Does anyone used Chakara core? How does it compares itself with V8?

Well if you are looking for a huge dataset, I would suggest stack overflow.

https://archive.org/details/stackexchange

I remember I wrote a node script to download all question and dump into my Postgres instance. It was fun, Postgres with an index could able to fetch results super fast

How many answers for this question?

How many questions are unanswered?

With gin index, I could do a free text search as well.

Slightly off topic but I see Go is better fit too. When i started learning go I read the source of Buntdb

https://github.com/tidwall/buntdb

It was very well written and easy to pick up as well.

I don't quite get this, you are saying Erlang is fault tolerant? I'm confused here because fault tolerance is something that the application using a particular language needs to make sure right? Sorry if I mistaken your statement.

Erlang and especially OTP "forces" you to follow a standard that usually results in highly reliable service powered by concise easy to read and maintain code.

Erlang comes with a philosophy/style on error handling, and its libraries help a lot as well.

Here's a reasonable summary: https://stackoverflow.com/questions/3760881/how-is-erlang-fa...

ferd did a great write-up on how Erlang approaches reliability:

https://ferd.ca/the-zen-of-erlang.html

It's more about assuming things will fail by default with good ways of handling it built-in at the language level. A lot of people also find its inventor's thesis enlightening. Here it is:

http://ftp.nsysu.edu.tw/FreeBSD/ports/distfiles/erlang/armst...

And for those concerned, there's also at least one project to write the native functions in a safer language to reduce their bugs a bit:

https://github.com/hansihe/Rustler

A lot of these concepts have been carried forward to some popular frameworks and languages. Akka (or Akka.Net & Akkling), is a great example. Railway Oriented Programming (https://fsharpforfunandprofit.com/rop/), has gained some traction in the .net sphere and, along with F#'s Result<'success, 'failure> type, emphasizes structured and exception-less error handling.

It may be a poor mans Erlang, but better than nothing ;)

It's the whole ecosystem with Erlang, OTP (Open Telecom Platform) and how they work with supervisors and monitors etc.

Everything is built so that you can operate a telecom switch and never drop that emergency call.

Erlang (Ericson language) is not necessary, you can also program for this in Elixir, although personally I prefer Erlang.

Look up the OTP Supervision trees

That's excellent point. When I digged into express source I understood several things like how it extends the response object via prototype to add methods like send etc. Also you will understand how exactly next function is implemented and then you can literally understand anything about the library.