Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to Safari
Join our communityTop Con
•••Top Con
•••Top Con
•••Top Con
•••
While starting with Heroku is fast and easy, and the first few deployments are actually very fast, larger applications tend to have slower deployments. It takes some time for the dynos to restart and while they are restarting the application is completely offline. Which means that you can lose precious seconds of application time. See More
The deployment process with AppFog is generally nice and easy because of its CLI. Unofrtunately the only downside of that process is the fact that it takes too long. A deployment to AppFog genereally takes up to 40 seconds, which should be fine if you are deploying once a week, but when you deploy every hour it starts bothering you too much. See More
The deployment process in Modulus can be slow depending on the size of the project. On every deploy the whole application is bundled (except node_modules and deployed to Modulus. Since it doesn't use something like git it has to upload every file on each deploy instead of "diffing" them. See More
Other than plain-text JavaScript files (which are the majority), modules can also be platform-specific binary images which are compiled at install time, usually by Python or node-gyp. Since Azure services run on a Windows-based system, for native modules to work they need to have been installed and compiled on a Windows development system. This prevents you from using some modules which have very specific requirements. But the most popular ones (like MongoDB) are able to run just fine. See More