Node.js on Google App Engine Goes Beta • Hacker News Board

Re: Node.js on Google App Engine Goes Beta

#91

Post by edwinnathaniel » Tue, Mar 22, 2016, 5:09 AM UTC

boulos wrote: post #79

edwinnathaniel wrote: post #70

Earlier quoted context omitted.

Hi Justin, I'm currently trying to get my feet wet on GAE. Judging from your statement, are you suggesting that people should look into Managed VMs and maybe skip the regular GAE (or known as the original GAE)? Perhaps the original GAE will be deprecated in the future?

No, that's not the case. Managed VMs is a more flexible environment than our "GAE Standard" environment, but (at least currently) comes with some of the tradeoffs of a full VM (startup time, minimum size, etc.). If you've got say a vanilla python app that doesn't need custom native modules, GAE Standard is great! If you want to run something we don't currently support, then Managed VMs gives you the flexibility a Com…

Thanks for the info @boulos. I've been watching GCP division quietly building solid products and ecosystems while the limelight shine towards AWS and Azure to some extend.

I'm also very excited to see GCP people responding to any GCP questions and/or clarifying its past "reputation" with a calm manner ;). Clearly the tide has changed (probably comes from the top too? :)).

Me and my partner are planning to invest a significant amount of time to the GCP ecosystems!

Re: Node.js on Google App Engine Goes Beta

#92

Post by dang » Tue, Mar 22, 2016, 6:09 AM UTC

jorgecurio wrote: post #83

brazzledazzle wrote: post #68

Earlier quoted context omitted.

They aren't nitpicking, it's a shitty thing to say. Period.

grow a thicker face

We've banned this account for repeatedly violating the HN guidelines.

Re: Node.js on Google App Engine Goes Beta

#93

Post by PostThisTooFast » Tue, Mar 22, 2016, 6:42 AM UTC

davidjgraph wrote: post #58

So many negative views of GAE, I have to add our, overwhelmingly positive, experience. We were paying $200/month for a load balanced EC2 setup in 2011, that's for around 2k unique daily users. The load balancer kept on false triggering new instances, so we went to GAE in 2012. Since then our uptime has been horrifically good, heavily thanks for GAE, trashing that of our competition, who mostly use AWS. Last month we…

Amazon is a mess. But should we care if Node is on Google? What about this: https://news.ycombinator.com/item?id=4495101

Re: Node.js on Google App Engine Goes Beta

#94

Post by sspross » Tue, Mar 22, 2016, 7:13 AM UTC

boulos wrote: post #54

esilverberg2 wrote: post #43

I wrote about my (unsuccessful) app engine experience many years ago...hopefully they've improved since then. http://www-cs-students.stanford.edu/~silver/gae.html

Good writeup! I think the main change is that App Engine has really morphed into a "You know, you don't have to use Datastore". Cloud SQL was added precisely because of the issues you raise: being on App Engine meant being in a totally foreign world, and not being able to get out easily. If you were to try again today, you'd take stock Django 1.9 via pip install Django -t lib and using vendoring: https://cloud.google…

It sounds like you know what you're talking about. Would you mind to take a look at my issue/question on the appengine django skeleton[1]. The Problems start after you've pointed your database to cloud sql und start using GAE specific features like task queue etc.

[1] https://github.com/GoogleCloudPlatform/appengine-django-skel...

Re: Node.js on Google App Engine Goes Beta

#95

Post by [deleted] » Tue, Mar 22, 2016, 7:42 AM UTC

boulos wrote: post #16

ungzd wrote: post #8

Quirkiness of Javascript + extreme weirdness of App Engine (especially datastore) = best of both worlds.

Aww, I like Datastore. But , there's no requirement that you use Datastore. The point of App Engine is that it's "you just give us code, we run it for you". With Managed VMs (built on top of Compute Engine) we're able to offer that programming model with a more flexible environment. As someone mentioned elsewhere, there's even "just hand us a random docker container". We've had people run ffmpeg because you can just…

[deleted]

Re: Node.js on Google App Engine Goes Beta

#96

Post by TheLogothete » Tue, Mar 22, 2016, 8:30 AM UTC

thesandlord wrote: post #26

smegel wrote: post #21

Interesting things are happening to GAE these days. They are moving towards custom runtimes using docker that the user can configure...even their datastore API is being replaced by something resembling S3. GAE -> Google Cloud Platform.

Cloud Datastore is more like DynamoDB, not S3. Cloud Storage is like S3. Yay names! Custom runtimes are trying to give people the "No Ops" of App Engine with the flexibility of Compute Engine. Like always, there are tradeoffs, but more options is usually better :) (I work for Google Cloud Platform)

Do you work on the database products? Please, PLEASE collaborate more with the analytics team. We want export to BQ for regular accounts. It's not a big ask and it will improve the lives and businesses of MANY people. I think it will affect google cloud revenues quite positively too.

Re: Node.js on Google App Engine Goes Beta

#97

Post by fibo » Tue, Mar 22, 2016, 8:47 AM UTC

Great news!

Re: Node.js on Google App Engine Goes Beta

#98

Post by IanCal » Tue, Mar 22, 2016, 8:58 AM UTC

bduerst wrote: post #78

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…

Why didn't you use managed VMs?

Well, managed VMs were only launched in 2014, so they may have migrated away before the launch. Even now they're still in beta, so I'm not too shocked at someone avoiding migrating from one platform they have issues with to a similar one with the same provider but which is only in an alpha state.

Re: Node.js on Google App Engine Goes Beta

#99

Post by pygy_ » Tue, Mar 22, 2016, 9:03 AM UTC

ionwake wrote: post #55

avar wrote: post #40

Earlier quoted context omitted.

> 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 warni…

Well for some reason I can't seem to be able to delete my comment, so I guess there isn't much I can do =(

The edit window is open for one or two hours.

Re: Node.js on Google App Engine Goes Beta

#100

Post by tomh- » Tue, Mar 22, 2016, 9:19 AM UTC

justinblat wrote: post #56

Greetings folks, I'm the PM for Node.js on App Engine. If anyone has any questions, feel free to ask me anything!

I have one, how can European individuals use the paid version of any Google cloud services? Last time I checked only commercial entities were allowed to use the paid version.