You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
JavaScript is everywhere now. Browsers, servers, desktops, mobile devices, robots. That is great! And it will be taken to even more places for sure. However, once JavaScript code is running on a given environment, it is constrained to continue running on that environment with the same available data and processing resources.
Although this constraint is not a problem for conventional applications whose location and allocation of resources are predefined and controlled authoritatively, it does create some barriers when considering different programming paradigms that would give applications the autonomy to decide where to run and look for less described, unexposed, unindexed data.
Then, what if in addition to running JavaScript code in many different environments, we could give it the ability to autonomously move from one environment to another while running? This talk will show how to use a module called JSFly to write code capable of migrating autonomously between Node.js servers, and discuss some possible applications like locally querying unexposed, distributed databases, and exploring the Web with non-HTTP crawlers.
The text was updated successfully, but these errors were encountered:
JavaScript is everywhere now. Browsers, servers, desktops, mobile devices, robots. That is great! And it will be taken to even more places for sure. However, once JavaScript code is running on a given environment, it is constrained to continue running on that environment with the same available data and processing resources.
Although this constraint is not a problem for conventional applications whose location and allocation of resources are predefined and controlled authoritatively, it does create some barriers when considering different programming paradigms that would give applications the autonomy to decide where to run and look for less described, unexposed, unindexed data.
Then, what if in addition to running JavaScript code in many different environments, we could give it the ability to autonomously move from one environment to another while running? This talk will show how to use a module called JSFly to write code capable of migrating autonomously between Node.js servers, and discuss some possible applications like locally querying unexposed, distributed databases, and exploring the Web with non-HTTP crawlers.
The text was updated successfully, but these errors were encountered: