Thoughts about the cutting-edge of server programming
Micro-services are the coming absolute standard in server architecture. Dividing a program up into smaller pieces has always be one of the principles of computer science, but to take it one step further and to have different parts of the program in different machines use to be only in the realm of super-computing. Cheap cloud-computing allows everyone to easily create their own clusters, and micro-services are the best architecture.
Of course our queries are RESTful, but we chose to use a simplified form. The requests are URL-queries, and it seems that the lowest common denominator for how long they can be is 2k characters (to be accessible to all browsers). The responses, though, are always in JSON.
Go is an incredible language whose standard library has enough components to satisfy 90% of one's needs. One can think of it as an improved C, so it lacks inheritance, function overloading, and generics. I hope someone creates a fork called Go++. I did some tests, the Go HTTP component was 80% as fast as Nginx, but they were only simple page loads, since Nginx's scripting language is not that complete.
Node.js is the most powerful way to do server-side scripting. Tens of thousands of packages means that one hardly has to write any code. And the speed is pretty decent, but do not even try to do anything CPU intensive. Node.js is JavaScript which is compiled with the V8 Engine and single-threaded.
I also realized the differences between concurrency and parallelism. When there is only 1 CPU, it is not possible to have parallelism. Parallelism includes concurrency, but concurrency is not parallel.
not really.
By the way, have a look at http://blog.plataformatec.com.br/2015/06/elixir-in-times-of-... . Elixir/Erlang excels at concurrency and allows you to build large-scale distributed backends easily, with many additional benefits (fault tolerance, ...).By the way, "Microservices" and "Actors" for parallelism and concurrency aren't really discussed in the erlang/elixir world, since this is the natural way to code. The "cutting edge" to do massive backends is actually decades old, battle-proven and guaranteed to work, this is what erlang actually was designed for.
Many many Big systems today are using the Erlang VM for their critical backends, like Call of Duty or Whatsapp.
Other than that, I agree.
I worry when I read comments like this.
Micro-services are an architectural style that should be used appropriately, not religiously, no matter what your favorite blog is telling you.
this is exactly what's wrong with the Node community.
EDIT: Mea culpa, it used to have. (ref. http://stackoverflow.com/questions/29428318/why-did-rust-rem...)
Well, you can always build your own interfaces to achieve a similar result. But why do you need go-routines ?
By the way, at least, Rust tries to handle concurrency the most he can (by analyzing if data race can occur, at compile-time for example).
What do you need more ?
Anyway, like you've said, the ecosystem is still maturing. But the more people are interested in Rust, and the more libs we will have.