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

Serverless Docker Beta

zeit.co

Post reply on HN
Print view View original

201–210 of 236 posts

Re: Serverless Docker Beta

#201

Post by tango12 »

tfolbrecht wrote: post #152
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.

Should be very easy for heroku to add serverless containers then. Their cold-starts for their free tier is a few seconds and works quite well.

Re: Serverless Docker Beta

#202

Post by crummy »

artursapek wrote: post #49
akx wrote: post #22

Earlier quoted context omitted.

If you connect to your database over TLS (maybe with an extra client certificate or something), I don't see much of a problem.

You don't see a problem with talking to your DB over the public networking, with long round-trips?

That's the service that mlab.com offers (which we use and are happy with). It does mean you have to be a little careful about your queries though, and cache if necessary.

Re: Serverless Docker Beta

#203

Post by arunoda »

skrebbel wrote: post #56
Rauchg wrote: post #12

Earlier quoted context omitted.

Most databases are quite unfit for the serverless world that's becoming a reality, where the needs shift towards global replication, flexible horizontal scalability (sharding) and vertical (provisioned QPS). We like and use CosmosDB because it fits this criteria. We anticipate that Google Spanner, CockroachDB and similar databases will become the go-tos in combination with ZEIT Now.

So what do most of your current customers do for data storage? I mean, I doubt they all use CosmosDB? (simply because it's not particularly mainstream)

We don't have insight on what our customer's use mostly.

We use existing technologies. Anyone can use any cloud Database service. We've datacenters on San Fransisco and in Belgium. So, based on those users can choose where they need to deploy their DBs.

Usually we recommend to configure databases via env variables. Users can also use our [now secrets](https://zeit.co/docs/getting-started/secrets) service as well to avoid hard-coding secrets.

Re: Serverless Docker Beta

#204

Post by rdslw »

andrewtorkbaker wrote: post #31

And so ZEIT, my favorite serverless provider, keeps getting better. Highlights: - "sub-second cold boot (full round trip) for most workloads" - HTTP/2.0 and websocket support - Tune CPU and memory usage, which means even smoother scaling And all that for any service you can fit in a Docker container - which is also how you get near-perfect dev/prod parity, an often overlooked issue with other serverless deployment te…

Count me in as a over-engineering and selling-things-engineers-do-not-need hater.

The very list of benefits on ZEIT, mentions 4 things: first two of them are clear over-engineering bloat (plus premature optimization), and second two were actually created only because of serverless. They were (and nothing more was mentioned in section benefits ;) :

* Clusters or federations of clusters * Build nodes or build farms * Container registries and authentication * Container image storage, garbage collection and distributed caching

I don't know why everybody can't see fakeness of argument'you need clusters, farms and hundreds of servers'. You don't. Actually you do only (contrary to your statement), if you're FANG.

Why? Because look at real world HUGE examples. E.G. stackoverflow (and no, your company/startup/whatever, will not reach their level of traffic) can do everything on literally dozen of servers, while they admitted that in some scenarios 1 web server was enough. Source: https://nickcraver.com/blog/2016/02/17/stack-overflow-the-ar...

Our 10x..100x smaller companies would perfectly do on 2..4. There is no need for whole over-engineering.

The ultra funny thing is ZEIT selling 'deployment self-heal' as old known (windows anybody) and ridiculed recipe: it will work after restart. Right. It's better to shut off car engine, go out, go in, and start again. This is XXI engineering :)

Re: Serverless Docker Beta

#205

Post by arunoda »

ingenieroariel wrote: post #61

I am already running an API service on Zeit now using a golang container that adds the binary and a csv file to a scratch image and re-reads the csv on each request (all requests take less than 0.3 seconds so i have not optimized). Currently I have to make sure to set min instances to 1 on the 'production' version of the API and set min instances = 0 to older versions. Will have to try before knowing for sure but I s…

You can alias your deployment and try to add a scaling rule to the alias.

So, you don't scale up and down as you deploy. Once you call the `now alias` it'll take care of the scaling.

Re: Serverless Docker Beta

#206

Post by ex_amazon_sde »

justicezyx wrote: post #187
andrewtorkbaker wrote: post #31

And so ZEIT, my favorite serverless provider, keeps getting better. Highlights: - "sub-second cold boot (full round trip) for most workloads" - HTTP/2.0 and websocket support - Tune CPU and memory usage, which means even smoother scaling And all that for any service you can fit in a Docker container - which is also how you get near-perfect dev/prod parity, an often overlooked issue with other serverless deployment te…

Where the fang devs mock come from? They are on the forefront of serverless.

Amazon does not use docker, ansible, salt and other hipster stuff internally because they are a nightmare to maintain at that scale.

Everything is deployed as immutable infrastructure.

Re: Serverless Docker Beta

#207

Post by Drdrdrq »

nickik wrote: post #115
SamLevin88 wrote: post #92

Earlier quoted context omitted.

mind elaborating a bit?

There are still servers involved. Serverless sounds like its peer to peer. What it really is is VM less.

Well, as a developer I don't need to concern myself with servers, so in a way the term is fitting.

Re: Serverless Docker Beta

#208

Post by tempodox »

Sujan wrote: post #73

Am I the only one having problems to follow .gif "demos"? When I get to the image, it is in the middle of everything and I don't really have an idea what is going on. Even watching it multiple times, I am not sure where it starts, ends, what the individual steps are. Or is it because I just don't know enough about this stuff?

“Don't hold it like that!”

Re: Serverless Docker Beta

#209

Post by rustyboy »

stingraycharles wrote: post #76
tlrobinson wrote: post #72

Earlier quoted context omitted.

Some platforms like Amazon Lambda let you set up functions to consume data from a variety of event sources: https://docs.aws.amazon.com/lambda/latest/dg/invoking-lambda...

How can I consume the Twitter stream API using that?

It depends what you're doing with that stream, most basically you would create a nano/micro EC2 instance that will just trigger Lambda events on every new tweet. Or you could create some more intricate script that does a lot of pre-processing and then stores it in RDS or S3, and with each new update to either of those sources kick off a Lambda.

Re: Serverless Docker Beta

#210

Post by nickik »

Drdrdrq wrote: post #207
nickik wrote: post #115

Earlier quoted context omitted.

There are still servers involved. Serverless sounds like its peer to peer. What it really is is VM less.

Well, as a developer I don't need to concern myself with servers, so in a way the term is fitting.

The interface it gives you is the functionality that the server provides. A server does not mean 'operating system'. you don't have to deal with the OS, but you still have you app running on the server.
Post reply on HN