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

Serverless Architectures

martinfowler.com

Post reply on HN
Print view View original

141–149 of 149 posts

Re: Serverless Architectures

#141

Post by icebraining »

osipov wrote: post #84
gmazza wrote: post #48

Earlier quoted context omitted.

Why not? RedHat will let you run arbitrary binaries just fine on OpenShift - both long-running/worker/"PaaS" and on-demand/per-request/"FaaS". Obviously this is tightly locked down with cgroups.

How would you modify systemd unit files for each user of your public cloud? How would you manage the sockets once you have more users than sockets on a server?

You can create systemd units using the D-Bus API instead of files, though I'm not sure those can be socket-activated.

As for having more users than sockets, is that really likely, considering there are 64000 available ports?

Re: Serverless Architectures

#142

Post by icebraining »

osipov wrote: post #43
jlward4th wrote: post #40

In regards to Stateless and 12 Factor... > This has a huge impact on application architecture, albeit not a unique one - the ‘Twelve-Factor App’ concept has precisely the same restriction. While 12 Factor does say that processes should be stateless I've never thought it really meant it. Connection Pools and in-memory caches are pretty typical in 12 Factor (or all non-serverless) apps. And for me that is what makes se…

Serverless apps should be stateless but should work in conjunction with stateful apps. Unlike Heroku, Cloud Foundry, OpenShift, and other traditional PaaSes focused on supporting long running applications and services, serverless frameworks offer a new kind of a platform for running short lived processes and functions, also called microflows. The distinction between the long running processes and microflows is subtle…

But how is this different from coding in, say, Django?

In Django you write a "view", which is just a Python function that is started when an HTTP request is received, and terminates by returning an HTTP response object. Then there are models, but these are just a translation layer between the Database and the view function, they don't keep state either.

I don't see how a Django view isn't a "microflow". It seems to me that the architecture is exactly the same, it's just that you don't get to choose the web framework.

Re: Serverless Architectures

#143

Post by cbd1984 »

vgt wrote: post #83
stickfigure wrote: post #77

By this definition, we've been running "serverless" on Google App Engine for most of a decade. * We don't monitor how many instances are running and don't really care. Our "functions" are http endpoints. GAE spins up or down instances to meet the load. Our interface with "instances" is just the size of the bill at the end of the month. * Async task processing is also just an http endpoint function. We even have a lit…

Oh buzzwords... We've been discussing Google BigQuery as serverless lately. It's a nice succinct way of saying "fully-managed" + "no-ops" + "no resource deployment" + "seamless scaling" + "separation of storage and compute" + "deployed regionally" + etc. Some customers talk about BigQuery as "Data Center is the Database". So these buzzword help describe what BigQuery is and how it is different from other analytics se…

Eh, literally everything can be a buzzword. "Email" has been a buzzword in the past, as has "Internet" and "mobile phone" and so on.

Re: Serverless Architectures

#144

Post by LionessLover »

amelius wrote: post #16

The article totally skips (serverless) federated architectures, which are more interesting, in my opinion.

At the bottom of the article:

> This is an evolving publication, and I shall be extending it over the coming days and weeks to cover more topics on serverless architecture including some things commonly confused with serverless, and the benefits and drawbacks of this approach.

You can send a tweet to the author: https://twitter.com/mikebroberts

Re: Serverless Architectures

#145

Post by tete »

cbd1984 wrote: post #143
vgt wrote: post #83

Earlier quoted context omitted.

Oh buzzwords... We've been discussing Google BigQuery as serverless lately. It's a nice succinct way of saying "fully-managed" + "no-ops" + "no resource deployment" + "seamless scaling" + "separation of storage and compute" + "deployed regionally" + etc. Some customers talk about BigQuery as "Data Center is the Database". So these buzzword help describe what BigQuery is and how it is different from other analytics se…

Eh, literally everything can be a buzzword. "Email" has been a buzzword in the past, as has "Internet" and "mobile phone" and so on.

Eh, no. Actually they weren't. A mobile version of a phone makes as much sense as electronic mail. Cause that is what it is.

It's not like web 2.0 which isn't a newer version and also not like serverless when it has servers or cloud which isn't a cloud.

Btw. this isn't about how new it is. Just look at stuff from the 90s. The terms they also didn't stick.

Also those things had a specific well defined meaning.

Like again web 2.0 didn't. User created content, Ajax, etc. all surround that.

Not saying buzzwords can't become meaningful, but they are still buzzwords.

Also they still are wrong when they are something like serverless, which is just plain wrong.

Re: Serverless Architectures

#146

Post by brianwawok »

SpaceCadetJones wrote: post #113
gmazza wrote: post #14

Serverless = new name for PaaS. VPS (virtual private servers) were available (and largely ignored) for quite a while before 2006, when AWS came along with the catchy word "cloud". This single word changed everything. Same technology all of the sudden became cool, and everybody started using it. Maybe now it is the turn of PaaS [1] - call it "serverless" and folks finally start seeing all the benefits (true scalabilit…

I'm confused, how does "serverless" play into this? I opened this expecting something about p2p architecture

You don't run the server so I guess you can pretend it doesn't exist.

Kinda like s3... it involves servers, but you don't have to do anything. Its just a black box you put in or get out data. "Serverless" FaaS is just a place you park some code and it runs.

Yes the name is kinda dumb.

Re: Serverless Architectures

#149

Post by eazel7 »

Wrong. All wrong. Serverless is like what is the server standing on before the server? That is serverless. Peer to peer mesh discovery protocols, for example. Serverless implies no server. Buzzz buzzzzz buzzzz buzzzz. Sexless sex.
Post reply on HN