Table of content
You’re aching to send your app into the world to woo and wow people.
You’ve got Heroku running your backend, Netlify your frontend and Atlas your MongoDB.
Furthermore, you’ve slung all of this together in a bundle and tied it to your GitHub repository.
But keeping tabs on all of them can be tricky. You need to ensure that, when you push a toggle on Heroku, it won’t affect anything on Netlify or Atlas. Likewise, flicking a switch on Netlify could cause trouble for your Heroku or Atlas service.
There’s also the worry about whether this whole thing will hold up when it receives a sucker punch to the gut. What if the heat is turned up? Will your MEAN stack be able to roll with the punches? Or will it run to the corner and cower like a little coward?
What about uptime monitoring? It could be a mission to maintain if it’s split up among too many services. You could probably consolidate in an external dashboard, but that’s more overhead.
Furthermore, these services all slip you a bill at the end of the month.
And something chews at your orbitofrontal cortex. It’s nibbling at the dinner with friends, or that hot date, or the hackathon tonight.
You’re wondering when one of these companies, or all of them, will send out an email to announce a “price review” because they “care about customer satisfaction” and “want to offer you the best possible experience”.
It’s looming, and the thought puts a little damper on your spirits, like slugging back a tequila only to find someone had slipped sweetener into it.
This horse is sicker than it looks. Lead it outside and shoot it. There’s a better way.