Serverless Docker Beta • Hacker News Board

Re: Serverless Docker Beta

#151

Post by erik_seaberg » Tue, Aug 14, 2018, 10:41 PM UTC

CBLT wrote: post #58

watty wrote: post #6

Looks great for basic websites but it's missing the biggest and most difficult piece of cloud infrastructure. The DATABASE! Today you'd have to open up your cloud DB provider to the world since Zeit can't provide a list of IPs to whitelist. This is a showstopper for me unfortunately.

From what I've seen, when people talk about serverless there's 2 camps. Functions makes life easier camp. Serverless development and deployments have nicer properties which make them easier to reason about and eliminate entire classes of errors. Functions make edge computing possible camp. Serverless functions can be deployed in datacenters around the globe close to your users, offloading compute from your core and i…

You can't decouple validation from the datastore if you want to be certain that all the validation happens and none is ever bypassed or outdated.

It bugs me how many systems have opt-in correctness.

Re: Serverless Docker Beta

#152

Post by tfolbrecht » Tue, Aug 14, 2018, 10:43 PM UTC

tango12 wrote: post #121

So this is different from running docker containers on heroku because heroku has 1 to n autoscaling but not 0 to n? What are the other fundamental differences?

It's actually pretty similar to the Heroku free tier dyno "sleep" till there's a trigger, but it's stateless.

Different pricing, different ways of conceptualizing but from a user perspective that's a pretty good comparison.

Re: Serverless Docker Beta

#153

Post by fru2013 » Tue, Aug 14, 2018, 10:47 PM UTC

Is there support planned for using this in combination with docker-compose? If so would be sweet to see this integrated with Prisma - https://www.prisma.io/

Re: Serverless Docker Beta

#154

Post by orf » Tue, Aug 14, 2018, 10:52 PM UTC

simonw wrote: post #63

orf wrote: post #23

Earlier quoted context omitted.

Sure, but I reached out nearly a year ago to the maintainers with no reply. It seems anyone can now execute anything on your infrastructure (for free!), which isn't great.

That's the case already: anyone can sign up for a free Zeit account and deploy code (wrapped in a Docker container) that then executes on Zeit's infrastructure.

And now someone can do it without signing up, using someone else's account, possobly disabling a widely used and quite cool service.

Re: Serverless Docker Beta

#155

Post by williesleg » Tue, Aug 14, 2018, 10:52 PM UTC

It looks like they run commands on a server.

Re: Serverless Docker Beta

#156

Post by gcb0 » Tue, Aug 14, 2018, 10:53 PM UTC

metamet wrote: post #144

legostormtroopr wrote: post #122

Earlier quoted context omitted.

Even better - make it an ASCIInema which gives you all that... and the ability to record from bash and copy and paste commands !

Was it intentional to make ASCIInema sound like "ass enema"?

thanks. now I will never be able to unsee that.

Re: Serverless Docker Beta

#157

Post by carimura » Tue, Aug 14, 2018, 10:56 PM UTC

jpetso wrote: post #148

dfischer wrote: post #109

Earlier quoted context omitted.

Facebook, Apple, Netflix, Google

I still find Netflix a curious addition to that list.

for the acronym.

Re: Serverless Docker Beta

#158

Post by [deleted] » Tue, Aug 14, 2018, 11:16 PM UTC

tfolbrecht wrote: post #143

Awesome! While I was at AWS Summit in NY, I asked a round circle of AWS ECS/EKS users (Container orchestration products) about thoughts on a Docker container service that could execute like a FaaS product and there seemed to be none anyone knew of. I have a portion of a legacy application that's used infrequently and too costly to decompose but works fine Dockerized. Looking forward to using your product!

[deleted]

Re: Serverless Docker Beta

#159

Post by zackbloom » Tue, Aug 14, 2018, 11:31 PM UTC

jazoom wrote: post #124

a17anxx wrote: post #105

Earlier quoted context omitted.

At Cloudflare, we're working on expanding Workers ( https://www.cloudflare.com/products/cloudflare-workers/ ) to allow access to your existing DB servers & offer protection with Argo Tunnel ( https://www.cloudflare.com/products/argo-tunnel/ ). We are also enabling Workers to write into Cloudflare’s globally distributed cache, reducing retrieval time for repeated query results. We hope this will be a differentiator wi…

Can your workers run Docker containers?

Workers don't run Docker containers intentionally. The goal with Workers is to run with a lower memory overhead (~3 MB) and lower startup time (~5 ms) than you can get with full container isolation. This allows your Worker to run affordably in 150+ locations around the world. In many ways it's the ultimate destination for serverless, running code in a multitenant process where all you manage is your code.

Re: Serverless Docker Beta

#160

Post by jshen » Tue, Aug 14, 2018, 11:31 PM UTC

driverdan wrote: post #68

stingraycharles wrote: post #53

Earlier quoted context omitted.

Not parent, but I have the same question; I worked in adtech and video analytics before, now with social media. It's usually a mix of some REST APIs, which already are very easy to scale and manage without using serverless, with long-running backend processes, such as: * video encoding; * ETL processes; * other analytical workloads; * long-running websocket connections with Twitter/Facebook/etc APIs. From my perspect…

Serverless is fantastic for ETL and data analysis, especially for workloads that vary in scale (eg cronjobs). Feed data in, get data out with scaling as needed.

but how do you feed data in? Usually, it's some other service on one of the big 3 cloud providers. I'm using google for my projects these days so it's a mix of Google PubSub and Dataflow.

I think this is the issue/risk with serverless. You either get locked into one of the big 3, or you end up doing all of the ops work to run your own stateful systems. As some of the people above you said, managing and scaling the stateless HTTP components is not the hard/expensive part of the job.