I have come to the following statement in the Arango Community website, Trapexit:
Erlang is a programming Languages are used to create large-scale scalable soft real-time systems with requirements on high availability.
In addition, I remember that Twitter has switched from Ruby to Scala to solve the scalability problem.
So, I wonder what is the relationship between programming language and scalability?
I would think that scalability depends on system design, exception handling, etc. Because of this, a language has been implemented, for libraries, or for some other reason?
Thanks to the hope for knowledge. Running up to 59's uptime or so, Along is highly optimized for a telecommunications environment. There is a set of libraries called OTP, and 'on the flight' without closing the application.
This is definitely possible in other languages. In C ++, you can reload DLL on the fly, load plug-in. In the python you can reload the module. In C #, you can load the code in on-the-fly, use reflection and so on.
It is this functionality that has been created in Erong, which means that:
- This is more standard, any ARL developer knows how it works
- Less content to re-apply itself
He said that there are some fundamental differences between languages, to some degree which is interpreted as something Bytes run, some are compiled indigenous, so run on performance, and type of information and so on. Aim is different.
Python has a global interpreter lock around its runtime, the library can not use SMP.
The ARLing recently made changes to take advantage of SMP.
Normally I agree with you, I think that a significant difference is less rather than a fundamental difference between languages rather than underlying libraries.
Eventually, I think that any project which is facing huge risk is 'stuck', it does not matter in T-language. As you say that I feel architecture and design, is very original for scalability and when I choose one language on another, I do not feel magically amazed scalability ...
No comments:
Post a Comment