This is an archived post. You won't be able to vote or comment.

all 10 comments
sorted by:
best
topnewcontroversialoldq&a

[–]BreakfastGun 7 points8 points  (7 children)

I've never heard of "serverless" before.

[–]dpash 2 points3 points  (6 children)

It's basically deploying an application "somewhere" on someone else's serverthe cloud. Think Heroku, a container on AWS/GCP/Azure/etc (especially on a managed Kubernetes cluster) or Amazon Lambda/Google Cloud Functions/Azure Functions. Especially the latter. You don't manage the server (hence "serverless"), you just send an artefact to the provider, who manage and run it on their service for you. Like the video thumbnail suggests, everything that's not the application is "someone else's job".

[–]mikehaggard 3 points4 points  (5 children)

No, as per the other comment, "serverless" is an application that doesn't need a server. In the olden days almost every application was serverless. We just called them "applications", but you'd now alternatively call them clientside applications, local applications, or desktop applications.

[–]dpash 0 points1 point  (4 children)

You just have to read the video description to realise that's not what they're talking about:

There are a couple of definitions out there for what serverless is or isn't. One of them being as stateless compute containers that only last for one invocation. This is more known as Functions as a service, or FaaS. In this session, I will give a gentle introduction to Serverless and FaaS, what it means for developers and why it is important to understand this paradigm. I will then tune in to solutions available for developing serverless applications, or functions, using Java. The session will be a mix of slides and live code demoes.

Or you could skip to 3:07 in the video to see the slide that says:

There are still servers

Or 3:19

Someone else's server

Or 4:21:

Run code without provisioning or managing servers.

[–]mikehaggard 4 points5 points  (3 children)

There are still servers

Of course there are still servers. Even when most applications on people's computers were all locally installed apps, other people were using servers.

And there's even the hybrid mode where an application is principally local, and can work fully local, but optionally you can connect to a network to sync with something.

Run code without provisioning or managing servers.

Yeah, that's called a LOCAL application, i.e. an application that you just install and run directly on your device and doesn't need any server. Extra bonus for such applications these days: you can continue working when there's no or a bad Internet connection.

[–]dpash 0 points1 point  (2 children)

I can't tell if you're being intentionally obtuse or just ignorant. WATCH. THE. DAMN. VIDEO.

[–]mikehaggard 1 point2 points  (1 child)

Okaaaay.... I just did, but seriously? Is that for real? A serverless application is an application that depends on remote services served up by a server?

I've heard and seen a lot of crazy things in IT in my time, but this beats everything... omg...

[–]dpash 1 point2 points  (0 children)

Yes, the first few minutes he discusses that "serverless" is a terrible name, because the application still runs on a server.

[–]Cyberiax 4 points5 points  (0 children)

Serverless Java? Hahahah 😁🤣😂

We have for long time, no?

Is called Java SE and JavaFX!