this is shitty. sorry about your business Nodejitsu, but you just lost us all.
Every Nodejitsu app is down
31–40 of 52 posts
Re: Every Nodejitsu app is down
#32Earlier quoted context omitted.
Can you please give some details because that's quite a damning statement for a company that professes to be build on enterprise ready infrastructure. I would default to be skeptical of statements like yours, everyone has downtime.
Here's what I can remember off the top of my head: - Deployments often fail with a nonspecific 500 error. I'd say near 50% of my deploys end up failing because of this. - Downtime occurs at random times. It's usually just a few minutes (maybe 10) - In the past I've had problems with certain routes always returning 500 errors when loaded in groups, but not alone. This problem hasn't happened for a while. - The admin p…
seconded. not to mention the rest..
Re: Every Nodejitsu app is down
#33Error handling in Node sucks. I hope they can find what is causing this.
This problem has nothing to do with node. It is a problem with a hosting service for node. JavaScript has exceptions. It has booleans. It has integers. What more do you need to handle an error?
Error handling is node is terrible due to a lack of consistency about errors. Any function can potentially either:
a) throw an exception, which will crash your app
b) emit an error event, which will crash your app if you aren't handling it
c) include the error in the first response of the callback
Domains are a knee jerk reaction to try and remedy this, but it's a pretty gross bandaid. I doubt that Nodejitsu's specific issues here are related to this, but it's one of the main reasons that I've moved away from building things in Node.
Re: Every Nodejitsu app is down
#34We are working on a major outage from our database provider, so, please, keep calm :) Our platform will be up asap. Check http://twitter.com/nodejitsu for updates. Sorry for the inconveniences and thanks for your patience.
A friendly word of PR advice: I'm not a customer and not affected by your outage, but if I were, being told to keep calm would really irritate me, especially if I were fighting fires right now. If you want someone to calm down, telling them to calm down generally won't have the desired effect.
Re: Every Nodejitsu app is down
#35this is shitty. sorry about your business Nodejitsu, but you just lost us all.
AWS, Heroku, and many other PaaS providers have had their own share of downtime occasionally. I see nothing so damning about this particular instance of PaaS going down that warrants complete abandonment of the platform.
Re: Every Nodejitsu app is down
#36Nodejitsu is incredibly unreliable. I use them only because they are so cheap and quick. Anything of value should not be hosted on Nodejitsu. This disappoints me greatly as Nodejitsu is a company i want to love.
I feel the same - intermittent short (1min) down times happen pretty regularly, about once a month, and I only know that from my own monitoring tools - no emails or notifications from them. I want to love them too :(
Re: Every Nodejitsu app is down
#37https://twitter.com/nodejitsu/status/321775765962240000 "Sorry for the inconveniences, we found that our database provider (@IrisCouch) is down at the moment, we are bringing up the cloud." I'm pretty surprised to learn that they don't run their own databases (and also that their database is CouchDB, but maybe I'm just old fashioned).
My two cents: CouchDB is great in that it allows you to remove the backend and rely solely on a database with REST baked in. However, it has its drawbacks, like database queries can be costly do to transactions over http. It's like every other argument in the community, how much control over ease do you want?
So you think these drawbacks are in someway related to the fact that they are offline? It seems like you are just jumping for a chance to kick a project and or spread some FUD.
Not to mention "database queries can be costly do to transaction over http" => Not gonna get into this too much, but couchdb has an optimistic concurrency model, yeah?
An implementation that uses a technology ( or like iriscouch is a db as a service) is not that technology. If heroku postgresdb's go down because they configure things incorrectly is that the fault of the project? Could be, could be documentation was lacking, or it was a real footgun. It is also possible to deploy technology within a budget where failures are the expected outcome, it is also very possible to deploy technology in a manner which does not support a use case, or may not even be something the technology can support, that does not make it 'bad' or 'great', and has nothing to do with "control vs ease" or http vs a yet to be named wire protocol...
I just don't see how this is helpful, accurate, or adds to the discussion, sorry if I am jumping down your throat about it.
Re: Every Nodejitsu app is down
#38this is shitty. sorry about your business Nodejitsu, but you just lost us all.
Speak for yourself.
Re: Every Nodejitsu app is down
#39A lot of people are talking shit about a service they've either never tried, or are paying $3 per drone per month for. Relax.
Having been with nodejitsu for 4 months now, I can say with confidently that they provide the best support out there. 24/7 IRC support with guys that go beyond the call of duty is worth way more than $3.
Yes, jitsu deploy used to have its 500 problems, but when we reduced our package size these all went away. We've had +98% deploy success for the last 4 weeks.
Yes, they are working on enterprise solutions, and if you're paying for enterprise, nobody forced you to buy into a provider that is less than 3 months old.
Nodejitsu have teething problems, but as far as I'm concerned, I'm happy with the experience, and nobody has a gun to my head to stick with nodejitsu if I didn't want to.
Re: Every Nodejitsu app is down
#40Looks like they were down for about 90 minutes maybe less