Deploying serverless Node.js microservices (Google I/O '18)

preview_player
Показать описание


#io18 event: Google I/O 2018; re_ty: Publish; product: Cloud - General; fullname: Steren Giannini, Myles Borins; event: Google I/O 2018;
Рекомендации по теме
Комментарии
Автор

Mixing Serverless and App engine in the same demo is quite confusing. As if all the cloud buzzwords were not confusing enough. If we go to Google's product page, they mention "Cloud functions" as in Beta and also do not suggest it for Web apps /APIs. In the demo, APP engine is portrayed as not having to decide infrastructure. However, it appears we have to choose the infrastructure for App engine.

RaoVenu
Автор

The "Task Scheduler" and the "Frontend" are accessing the same database. From my understanding there should be a Task Service that stores the tasks and then the "Task Scheduler" and the "Frontend" should only access the data through that service, right?

wacalu
Автор

AWS with Lambda seems to be ahead in this

electro_beatz
Автор

great, but pay as you go is not cheap, I would prefer renting a VPS and build what I need.

___OmerAJ___
Автор

Hasn't this been working for a while now? Like at least 6 months you could deploy node on app engine

kostaad
Автор

How about python? Node.js isn't that useful. Why has both Amazon and Microsoft support python, node.js, .net, and Google's own GO language while Google functions support one language. I would love to advocate for Google cloud services but it's difficult when it's services are so annoyingly half implemented.

DerekAndersonMinnesota
Автор

Why node 8 and not 10?
Why can't flexible environment scale to 0 as well?

ecereto
Автор

Azure is miles ahead of you guys :) And the logging reporting is a joke.

kostaad
visit shbcf.ru