Decisions 2

Michael R.
Full-Stack Web Developer at STHCoders
This decision is a follow-up to my previous request for advice
We ultimately decided to use Heroku
for the production build of the full-stack web application we built for Ormica LLC. React.js
, Node.js
, Express.js
The deployment had its share of issues; all of these I experienced firsthand. It would seem that Heroku
takes a stricter view than even most development environments to the slightest syntax issue or the tiniest bug. Not to mention their engineers are unavailable on weekends, even if you are using a paid subscription, which I found quite surprising.
But, as I have before, I will again give credit to their documentation for being extremely detailed and intuitive. Additional credit goes to Mars Hall for the use of his trusty heroku-cra-node template as the baseline for the application.
At the end of the day, I still recommend Heroku
for their thorough documentation, infallible uptime, and extensive plugin options.
Just be aware that if you missed anything in your code, the Heroku
build engine is going to find it for you. Every. single. time. Which, from an objective point of view, is actually a good thing. Thanks for reading!

Michael R.
Full-Stack Web Developer at STHCoders
We are preparing to deploy a MERN-stack application (PWA) for a client. The app will be a public-facing real estate platform for listing, buying, and selling homes. While presenting a user experience much like a website, it retains the scalability and functionality of a web application.
I am weighing the pros and cons of using Microsoft Azure over Heroku, especially now that Heroku no longer supports mLAB for connecting Mongo databases. See more Suggestions and feedback always welcome.