TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Beta release of PHP 7.2 in the Google App Engine standard environment

185 点作者 sl0wik将近 7 年前

10 条评论

sayhello将近 7 年前
This is exciting because the second generation standard environment allows Google App Engine to provide a more &quot;idiomatic&quot; experience.<p>Using gVisor, instead of NaCL, as the sandboxing technology, shipping new runtimes becomes a much more tractable task with less differences from the &quot;plain&quot; runtime. In fact, gVisor allows us to use the runtime unmodified.<p>This in turn, decreases the &quot;lock-in&quot;. There are still decisions we need to make depending on the runtime, e.g. which package manager to use if there isn&#x27;t a community default.<p>Hopefully, the narrative for &quot;Serverless&quot; moves beyond lambda and functions. Sometimes (!) we want apps, databases, caches and more to be &quot;Serverless&quot; :-)<p>Disclaimer: I work at Google, on the App Engine Runtimes team. I helped ship this
评论 #17813519 未加载
评论 #17812832 未加载
评论 #17813501 未加载
评论 #17819111 未加载
评论 #17811425 未加载
avolcano将近 7 年前
The state of App Engine environments seems super confusing, but I _think_ this uses the &quot;second generation standard environment&quot; like the Python 3.7 and Node 8 beta environments, which means that unlike App Engine of Yore, you have access to the full package ecosystem and full network access. I&#x27;m not actually 100% sure on this because it&#x27;s not listed on the runtime page (<a href="https:&#x2F;&#x2F;cloud.google.com&#x2F;appengine&#x2F;docs&#x2F;standard&#x2F;appengine-generation" rel="nofollow">https:&#x2F;&#x2F;cloud.google.com&#x2F;appengine&#x2F;docs&#x2F;standard&#x2F;appengine-g...</a>), but the docs show that you can use composer, unlike the PHP 5.5 runtime.<p>The documentation for all these second generation runtimes is shockingly bad. I consider Google to be _generally_ pretty good at documentation, but this is one of those cases where their propensity for confusing naming and classification of their products makes it hard as hell to figure out what is going on. It doesn&#x27;t help that the top-level &quot;product overview&quot; page is useless marketing junk (microservices! serverless!) instead of a practical description, which is buried several links deep.<p>Having never used App Engine but occasionally wandering into its docs when a new product gets announced like this, am I right in assuming that App Engine&#x27;s &quot;second generation standard environment&quot; is more or less equivalent to the feature set you&#x27;d get from Heroku? The flexible environment also continues to confuse me - it talks about being a managed Docker container, but it doesn&#x27;t seem like you actually get access to anything like a Dockerfile and that&#x27;s more of an implementation detail on their end.
评论 #17811409 未加载
评论 #17811569 未加载
评论 #17810892 未加载
sl0wik将近 7 年前
For those not familiar with benefits, it&#x27;s mainly about scaling from zero to heavy traffic fast. If for example, you are running CRM behind call center with crazy traffic during TV ads, and no traffic on weekend your infrastructure can scale from 0 to multiple instances instantly.
kyrra将近 7 年前
This is on the heels of the Python 3.7 AppEngine release from 2 weeks ago[0]. gVisor[1] (user-space kernel) seems to be ready for prime time, which is allowing rolling out new AppEngine runtimes waaay faster.<p>[0] <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=17717045" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=17717045</a><p>[1] <a href="https:&#x2F;&#x2F;github.com&#x2F;google&#x2F;gvisor" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;google&#x2F;gvisor</a>
andr将近 7 年前
What explains the vast price difference between App Engine standard and flexible environment? In the standard environment, $0.05&#x2F;hr gives me a 128MB, 600MHz container. Flexible environment is priced at GCE pricing, giving me 3.75GB and 1 vCPU for the same price, before even applying committed use discounts. It seems hard to justify using the standard environment, even if scaling up&#x2F;down is faster.
评论 #17813081 未加载
评论 #17813928 未加载
detritus将近 7 年前
Excuse my complete and total ignorance here - but is this essentially a &#x27;quick deploy&#x27; php instance? if so, what might a none-Google alternative be?<p>I&#x27;ve only ever &#x27;rolled my own&#x27;, on small-scale virtual or shared servers, but I&#x27;ve got an upcoming project I could do with trying to install on something completely seperate - something like this might fit the bill.<p>Or not!<p>Thanks.
评论 #17811060 未加载
评论 #17810953 未加载
评论 #17817493 未加载
评论 #17812411 未加载
评论 #17811064 未加载
评论 #17811353 未加载
评论 #17811996 未加载
评论 #17811707 未加载
arttii将近 7 年前
I was wondering what people generally think on using AppEngine when compared to rolling the API gateway+Lambda for public side projects. Somehow there seems to be much more movement on Lambda front, but I can&#x27;t seem to find a lot of opinions from people running their apps in app engine, which I am quite sure there are more than Lambda? Or am I mistaken? The standard environment seems to be quite feature rich, but with a lot of hidden limitations for a newcomer, but at the same time the developer story for Lambda is not that great at all.
评论 #17811893 未加载
评论 #17811857 未加载
vgy7ujm将近 7 年前
Now if they only would support Perl...
评论 #17814534 未加载
merb将近 7 年前
now .net core in standard environment!
bborud将近 7 年前
I feel slightly queasy :-)
评论 #17810874 未加载
评论 #17811420 未加载
评论 #17811171 未加载