Heroku - Experimental support for Node.js
Today we offer experimental support for node.js to a limited number of users. We know that there is a great demand, and we will work with as many users as we can support. Details below.
Yesterday we wrote about what we think about the platform, and what further action plan we have formed .
We are always looking for additional scenarios to support them, and lately we have thought a lot about real-time applications and event-driven architectures.
Today, most Ruby applications are synchronous. By default, all I / O operations are blocking. When you upload a file, poll a service, or wait for data, your application will be blocked. Although this can be fixed by carefully eliminating all blocking I / O from your code and dependencies, and using a library like EventMachine, for example, this is tedious and, as Adam points out, “Libraries like eventmachine will never become truly convenient. use, because event-driven input / output is a fairly fundamental shift that requires deep integration with the programming language. JavaScript, as it turned out, is a fundamentally event-driven language, because it has its roots in the browser. ”
')
Node.js is an event input / output engine for JavaScript, built on top of a super-fast V8 engine . This makes event I / O handling incredibly simple and fits perfectly with our manic desire for simplicity and developer productivity. The Ruby community quickly adapted Node, and with great effect. Complementing existing applications using node.js for components that require real-time event handling or mass parallel operations is easy and elegant — in part because of frameworks such as express .
Node fits well with our existing architecture. This is just another processing module available for selection as part of our stacks :
Node support opens up many questions about the platform: how will we install, which option will we support, how can I integrate it with my current applications? We are releasing it in an experimental state at the moment to collaborate with the Node.js and Ruby communities on this issue. Over the coming months, we will work together to answer all these questions and many others.
If you want to participate and use the node on an experimental basis, drop a letter to nodejs@heroku.com with your email address, describing what you want to use Node for, and we will work to include you in the program.
Natural add-on for Ruby
Yesterday we wrote about what we think about the platform, and what further action plan we have formed .
We are always looking for additional scenarios to support them, and lately we have thought a lot about real-time applications and event-driven architectures.
Today, most Ruby applications are synchronous. By default, all I / O operations are blocking. When you upload a file, poll a service, or wait for data, your application will be blocked. Although this can be fixed by carefully eliminating all blocking I / O from your code and dependencies, and using a library like EventMachine, for example, this is tedious and, as Adam points out, “Libraries like eventmachine will never become truly convenient. use, because event-driven input / output is a fairly fundamental shift that requires deep integration with the programming language. JavaScript, as it turned out, is a fundamentally event-driven language, because it has its roots in the browser. ”')
Node.js is an event input / output engine for JavaScript, built on top of a super-fast V8 engine . This makes event I / O handling incredibly simple and fits perfectly with our manic desire for simplicity and developer productivity. The Ruby community quickly adapted Node, and with great effect. Complementing existing applications using node.js for components that require real-time event handling or mass parallel operations is easy and elegant — in part because of frameworks such as express .
Easy to use
Node fits well with our existing architecture. This is just another processing module available for selection as part of our stacks :
Open questions
Node support opens up many questions about the platform: how will we install, which option will we support, how can I integrate it with my current applications? We are releasing it in an experimental state at the moment to collaborate with the Node.js and Ruby communities on this issue. Over the coming months, we will work together to answer all these questions and many others.
How to participate
If you want to participate and use the node on an experimental basis, drop a letter to nodejs@heroku.com with your email address, describing what you want to use Node for, and we will work to include you in the program.
Source: https://habr.com/ru/post/92404/
All Articles