|
Just means "someone else's server"
Like he said, "marketing BS"
>64
Some days the dragon wins. Suck it up.
|
|
|
|
|
You nailed it! That's exactly what it means and that's exactly why it's so confusing to people who actually understand technology.
See my answer at: The Lounge[^]
|
|
|
|
|
theoldfool wrote: Just means "someone else's server"
That's always been my own informal definition as well, purely based on my own guesses.
|
|
|
|
|
Here's what it actually means -- it means having someone else manage your servers where your stuff runs...
From the book,
Serverless as a Game Changer: How to Get the Most Out of the Cloud[^]
Quote: Serverless Means Not Our Uptime
One of the simplest definitions of Serverless, and the principal way I think about fully Serverless applications, is that the responsibility for keeping applications running is not the responsibility of the organization that developed the applications.
Yes, that's marketing -- not really technology!
|
|
|
|
|
Technically you can use lambda functions and be "serverless". But there's no server in the traditional sense at all. I didn't read the link mind you, but if they're suggesting it's just a server on the cloud executing code then that's not accurate.
Jeremy Falcon
|
|
|
|
|
The "centralized versus distributed" debate is an ongoing source of techno-marketing hype. Mainframes gave way to workstations gave way to servers gave way to desktops gave way to the cloud.
|
|
|
|
|
Real talk. There's a time and place for both concepts IMO. Anytime peeps talk about a blanket one way for all things, is usually when it's fluff.
Jeremy Falcon
|
|
|
|
|
Smorgasbord?
I don't think before I open my mouth, I like to be as surprised a everyone else.
PartsBin an Electronics Part Organizer - Release Version 1.3.0 JaxCoder.com
Latest Article: SimpleWizardUpdate
|
|
|
|
|
It means: someone else's server.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
So now if I break into your place, hang out on your couch and channel surf, i am "homeless"
What will marketing think of next?
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
There are micro-services ... so there must also be micro-servers out there.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
It doesn't run in the browser.
Distributed model
Client - API Server - Other services (database, etc)
Hardware model for the above
Client PC - Business PC - Services PC
Serverless
Client PC - Containerized App - Services PC
---------------------------------
For the standard model if your business gets busy you must increase the number of Business PC instances using some method (manual or dynamic modeled by you). Note that you can do dynamic sizing at least in AWS.
For serverless (ones I have seen) the midlevel is expanded automatically on demand without any need for you to determine that (basically - naturally there are management tools.)
---------------------------------
There is more overhead with starting up a new Cloud PC than with a serverless container.
Myself I would not trust it cost less except for immediate surge handling. Dynamic sizing as long as there is no immediate demand would probably cost less but one must then manage the dynamic modeling which is not very easy.
---------------------------------
Serveless has the problem that it is stateless. So for example if you want to cache database results you would then need yet another Services PC to do that.
Additionally surges might grow so big that it overwhelms the Services level. But that can happen with the Business level also without serverless.
It cannot be used for everything that you might normally put into the Business level. There are limits (at least in AWS). Again some of that might be reflected in real business needs to do it that way but could also just be poor design (but refactoring is often not an option.)
|
|
|
|
|
I'm not sure anyone knows. Its meaning probably depends on who you ask. lol
For me it means something like Azure Function apps, which are microservices/functions that execute on a server somewhere in Azure. You don't have to worry about the server, its setup or maintenance. They aren't full apps, just single-purpose functions that can receive or pass data or objects to other functions if needed. Your only concern is the code.
There are no solutions, only trade-offs. - Thomas Sowell
A day can really slip by when you're deliberately avoiding what you're supposed to do. - Calvin (Bill Watterson, Calvin & Hobbes)
|
|
|
|
|
The first paragraph in the book Azure Serverless Succinctly[^] by CP's very own Sander Rossel gives a good definition:
Quote: Serverless computing is a cloud service where the cloud provider dynamically allocates infrastructure to run your code.
There are no solutions, only trade-offs. - Thomas Sowell
A day can really slip by when you're deliberately avoiding what you're supposed to do. - Calvin (Bill Watterson, Calvin & Hobbes)
|
|
|
|
|
That kind of makes sense to me except my little VPS does the same thing, and I don't understand the difference.
Someone else explained it (I forget who now) as basically you're using someone else's server. That makes sense to me, although serverless != someone else's server, I at least understand it from a I guess a marketing? perspective even if it's a bit of a stretch.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
honey the codewitch wrote: It seems to be all the rage in web circles. This is no way related to me. Brainless maybe, but I'll have my applications with a server, thank you.
|
|
|
|
|
It is a way to simplify your deployment. The trade-off is it might cost you more money or save you some money depending on the traffic. It should always help with uptime/server-overload.
If you are supporting traffic that sees incredible spikes, then this could auto-scale to help support the load. (Think Black Friday/Cyber Monday for retailers)
If you have moderate, steady traffic, then it might not be worth it.
|
|
|
|
|
Have a good one:
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Indeed, have a good one!
"In testa che avete, Signor di Ceprano?"
-- Rigoletto
|
|
|
|
|
Happy birthday, buddy.
Jeremy Falcon
|
|
|
|
|
Happy day.
Have lots of birthdays, leads to long life.
>64
Some days the dragon wins. Suck it up.
|
|
|
|
|
Hmmm, I'm kinda worried about that sheep, especially after a few
|
|
|
|
|
dandy72 wrote: I'm kinda worried about that sheep
Well, dancing aliens and penguins aren't very common in The Netherlands...
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Penguins? Pretty sure that's one of Chris' famous badgers!
|
|
|
|
|
Well, it looked like a penguin to me...
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|