If only you offered Mongo with Galaxy. I’ve used Mongolabs with Galaxy successfully once, but nothing beats complete deployment with a one-line command.
As a subscriber of status updates, I did not receive a notice until after the outage was resolved.
Looking at status.meteor.com, as of this morning, it still lists the free tier as having partially degraded service.
It would be great if notices about downtime could be sent out when they happen, not afterwards. That could have, for example, avoided the need for this and other similar threads.
It would also be great if more detail could be provided on the status site.
In other words, perhaps all the recent & continued problems w/the free tier is a back-handed marketing ploy to push people into the outrageously expensive Galaxy platform? Might just kill off the stream of newcomers.
Galaxy developer edition is very reasonably priced, a 512mb instance should only cost you $13/month and you can hook up to a free mongo instance.
I highly doubt this outage by meteor is intentional and a marketing stunt.
Having said that, I’ll be moving off their ‘free’ offering permanently because the last couple of days have demonstrated just how much **** is given. None.
There is no communication, there is no ETAs and they try to cover up their downtime (Meteor saying they were down for an hour, my project wasn’t working for 3 days and counting).
‘Look at us, all other paid offerings are great, free is … degraded… sorry if you’re on free… cheapo’. Makes me feel like a second class citizen developing with Meteor.
Might be (not an expert on this) but it’s for sure not coming with a single line deployment that we get with Modulus, Compose or Galaxy, right?
That’s the biggest hurdle for me, surely there are cheaper options out there but I’m willing to pay someone to take care of basically everything and ensure my apps are running well all the time and in case something goes wrong, I don’t need to hunt at SO/Google for solutions and learn Unix or similar stuff.
That might be cheap if you have one app… or if you are making money making Meteor apps and charging people monthly fees… but if neither of those things apply… spendy.
Meteor app instances are expensive, any way you look at it… Apache threads… those are cheap.
I’m jumping the gun a bit saying this, but we are literally days from wrapping up some major work on Galaxy that will make it possible to offer our production-quality hosting to everyone. We’ve been trying hard to keep our focus on that work, so much so that we dropped the ball on posting updates here about the legacy servers.
If I can ask, please just hang tight over the w/e while we get some last details sorted. It’s going to be a big improvement!
(Glasser wrote a forum post a few months back with more color on what goes into running O(100k) apps. Worth the read.)
I knew I’d read that the issue was around the number of small databases somewhere! @a4xrbj1 this was what I was trying to refer to in the other thread.