Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Node.js on Google App Engine Goes Beta

cloudplatform.googleblog.com

Post reply on HN
Print view View original

31–40 of 114 posts

Re: Node.js on Google App Engine Goes Beta

#31

Post by mattbillenstein »

Don't use AppEngine. I migrated Homejoy off of AppEngine in 2014 and I can't recommend the platform for any reason whatsoever. It's slow, expensive, not based on OSS, and not particularly stable. Bits of it (urlfetch, search, etc) would go down for hours at a time and you're basically hosed until they fix it.

I think Heroku is usable with a similar level of effort -- and you have a much easier migration path to something else if you're not using Google's proprietary datastore IMO.

Re: Node.js on Google App Engine Goes Beta

#32

Post by adrianpike »

jorgecurio wrote: post #30

is anyone using node.js in enterprise? because everyone seems to be convinced that the enterprise companies are going to uproot all the network of partners, developers, vendors, and billions of dollars of investment made over the past decade? Like it or not, JVM pretty much rules the enterprise space and there's just no way to do it another way. Literally, you will be turned away because you told the IT department th…

Yes, we are, but caveat; it's only for a few smaller services where the functionality makes lots of sense to be heavily asynchronous, and we're not leveraging many external dependencies.

FWIW, deployment and packaging is still a painful issue for node - I've been bitten in the past by people not semver'ing their modules in a non-breaking way.

Re: Node.js on Google App Engine Goes Beta

#34

Post by dlor »

justinblat wrote: post #29
plexicle wrote: post #24

Earlier quoted context omitted.

Well, that's good at least. Must have been very recent, I was talking to support only a couple weeks ago.

I think technically that command is still hidden lol. You can run it, it just doesn't show up in the docs. We'll be officially releasing that one in a few weeks.

Although "gcloud preview app modules stop --version= is documented, and does the same thing.

Re: Node.js on Google App Engine Goes Beta

#35

Post by [deleted] »

mattbillenstein wrote: post #31

Don't use AppEngine. I migrated Homejoy off of AppEngine in 2014 and I can't recommend the platform for any reason whatsoever. It's slow, expensive, not based on OSS, and not particularly stable. Bits of it (urlfetch, search, etc) would go down for hours at a time and you're basically hosed until they fix it. I think Heroku is usable with a similar level of effort -- and you have a much easier migration path to somet…

[deleted]

Re: Node.js on Google App Engine Goes Beta

#36

Post by TheLogothete »

jorgecurio wrote: post #30

is anyone using node.js in enterprise? because everyone seems to be convinced that the enterprise companies are going to uproot all the network of partners, developers, vendors, and billions of dollars of investment made over the past decade? Like it or not, JVM pretty much rules the enterprise space and there's just no way to do it another way. Literally, you will be turned away because you told the IT department th…

Why do you think that people want to use it to build BREs?

Not everything in enterprises in a giant monolith. People make "apps" for various reasons.

Re: Node.js on Google App Engine Goes Beta

#37

Post by notliketherest »

ionwake wrote: post #5

All I know about GAE is that when my python app started being used by HN users I upgraded my account to a paid one to increase performance. In the transition , without any warning, google took the app down, for a day. Thus killing all chance of acquiring a userbase now that I had hit the frontpage. When I went onto the IRC GAE channel to ask someone for help to unlock or keep the app running during this important mom…

"For startups"

Well they say right there in the article: "App Engine provides developers with a great platform for building web applications and services that need to operate at Google scale."

Re: Node.js on Google App Engine Goes Beta

#38

Post by mattbillenstein »

mattbillenstein wrote: post #31

Don't use AppEngine. I migrated Homejoy off of AppEngine in 2014 and I can't recommend the platform for any reason whatsoever. It's slow, expensive, not based on OSS, and not particularly stable. Bits of it (urlfetch, search, etc) would go down for hours at a time and you're basically hosed until they fix it. I think Heroku is usable with a similar level of effort -- and you have a much easier migration path to somet…

Yes yes, downvote the only guy on this thread who has any real experience running a production app on AppEngine.

Re: Node.js on Google App Engine Goes Beta

#39

Post by eecks »

ionwake wrote: post #5

All I know about GAE is that when my python app started being used by HN users I upgraded my account to a paid one to increase performance. In the transition , without any warning, google took the app down, for a day. Thus killing all chance of acquiring a userbase now that I had hit the frontpage. When I went onto the IRC GAE channel to ask someone for help to unlock or keep the app running during this important mom…

That is pretty awful. Have you found an alternative that you can suggest?

Re: Node.js on Google App Engine Goes Beta

#40

Post by avar »

ionwake2 wrote: post #25
Strom wrote: post #17

Earlier quoted context omitted.

Do you remember the day when this IRC event took place or what nick you used? I have the logs, and would like to look into this. Also, when you say "staff member", do you mean Google's staff? The reason I'm asking is that I've been active in the GAE IRC channel for 6 years and I don't remember anything like this ever happening. I do remember a few cases where people have come with similar problems complaining that th…

Hi, Thanks for the reply. I would like to retract the statement that it was a member of staff, you are correct, this may have not been the case. It was a while ago and it may have just been someone in the know, who didn't actually work for google. I didnt expect anyone to even notice my comment. I should have been more careful with my statements. I will be removing the comment when HN allows me to log back in (appare…

    > I will be removing the comment when HN allows me to log back in.
In that case, here's a copy of your initial comment, because removing top-level comments that have ongoing follow-up discussion makes for very confusing discussions:

    > All I know about GAE is that when my python app started being used
    > by HN users I upgraded my account to a paid one to increase
    > performance.
    >
    > In the transition , without any warning, google took the app down,
    > for a day. Thus killing all chance of acquiring a userbase now that
    > I had hit the frontpage.
    >
    > When I went onto the IRC GAE channel to ask someone for help to
    > unlock or keep the app running during this important moment the
    > reply from a staff member was ' You should have planned better'. I
    > was surprised to hear this response and did not pursue the matter
    > further. Its all in the IRC logs if any of this sounds doubtful.
    >
    > TL;DR; Surprisingly, I did not find the GAE platform to be a
    > supportive environment for startups.
    >
    > ionwake @ ~2016-03-21 22:xx UTC
Post reply on HN