What Makes Something An Appliance
-
@Tim_G said in What Makes Something An Appliance:
Server: In computing, a server is a computer program or a device that provides functionality for other programs or devices, called "clients". This architecture is called the client–server model, and a single overall computation is distributed across multiple processes or devices.
Appliance: Computing devices with a specific function and limited configuration ability.
There IS some overlap. Both can be devices. Example: Dell R730xd and Microwave. One is an appliance, but not a server. One is an appliance for sure, and one has potential to be an appliance.
The limiting might be critical... but that makes nearly everything that people normally consider to be an appliance, not to be.
-
@Tim_G said in What Makes Something An Appliance:
@Tim_G said in What Makes Something An Appliance:
Appliance: Computing devices with a specific function and limited configuration ability.
There IS some overlap. Both can be devices. Example: Dell R730xd and Microwave. One is an appliance, but not a server. One is an appliance for sure, and one has potential to be an appliance.
So, we have two things defined with an 'and' statement: specific function AND limited configuration ability
I would like to add "intended" to make "intended specific function". Because with the FreeNAS example, that makes all the difference... intention. It's intended for a specific function, but is your ability to configure it limited?
No, not limited at all. Zero limits. Hence the maintenance of "100% general purpose" in addition to the "intention" of storage.
-
This is where I see Kace or NetApp as different.. they are limited AND specific.
-
@scottalanmiller said in What Makes Something An Appliance:
The limiting might be critical... but that makes nearly everything that people normally consider to be an appliance, not to be.
@scottalanmiller said in What Makes Something An Appliance:
No, not limited at all. Zero limits. Hence the maintenance of "100% general purpose" in addition to the "intention" of storage.
As long the definition I provided (from Wikipedia) is accurate regarding the "limited configuration ability" part.... but assuming it is...
Exactly! There are literally no configuration limits with FreeNAS.
Next step I think we need to define 'limiting'... limiting by what means? User/password limiting? Like in the KACE example, they won't give you the password to make configuration changes. Or, limited due to design... as in it's just not possible.
-
@Tim_G said in What Makes Something An Appliance:
Or, limited due to design... as in it's just not possible.
By that, I mean not possible as it is. It may be possible by installing more software, packages, addons, etc... but that's not it's original purpose.
-
@Tim_G said in What Makes Something An Appliance:
@scottalanmiller said in What Makes Something An Appliance:
The limiting might be critical... but that makes nearly everything that people normally consider to be an appliance, not to be.
@scottalanmiller said in What Makes Something An Appliance:
No, not limited at all. Zero limits. Hence the maintenance of "100% general purpose" in addition to the "intention" of storage.
As long the definition I provided (from Wikipedia) is accurate regarding the "limited configuration ability" part.... but assuming it is...
Exactly! There are literally no configuration limits with FreeNAS.
Next step I think we need to define 'limiting'... limiting by what means? User/password limiting? Like in the KACE example, they won't give you the password to make configuration changes. Or, limited due to design... as in it's just not possible.
That I'm not sure. To limit in the later sense would require.... well a lot and would always be a grey area. Name any system that is limited all the way to the kernel. If you can run code directly on the kernel, it's not actually limited. So NetApp and Kace would not be appliances either if we included that definition. I think that has to be too far, it just feels like an impossible goal. I literally know no appliance at that point.
I would say that the password / license / support restriction would be enough.
-
@Tim_G said in What Makes Something An Appliance:
@Tim_G said in What Makes Something An Appliance:
Or, limited due to design... as in it's just not possible.
By that, I mean not possible as it is. It may be possible by installing more software, packages, addons, etc... but that's not it's original purpose.
But what would be an example? All OSes require software added on to do things. The thing that makes something a general purpose OS is that you can run arbitrary code on it, not that it includes all potential functionality.
-
If we went by limits like that, then suddenly the tables would turn and Windows would be seen as an appliance by not including most functionality and requiring you to add it on. FreeNAS comes with pretty much anything you can imagine from databases to desktops. But Windows requires add ons for nearly anything. Suddenly the most often anti-appliance becomes the appliances and the appliances become the servers.
-
@scottalanmiller said in What Makes Something An Appliance:
@Tim_G said in What Makes Something An Appliance:
@Tim_G said in What Makes Something An Appliance:
Or, limited due to design... as in it's just not possible.
By that, I mean not possible as it is. It may be possible by installing more software, packages, addons, etc... but that's not it's original purpose.
But what would be an example? All OSes require software added on to do things. The thing that makes something a general purpose OS is that you can run arbitrary code on it, not that it includes all potential functionality.
Well, lets say you download FreeNAS and set it up on a physical or virtual server. You configure it for it's original purpose, as and only as a NAS. Now you password it, so nobody can make any configuration changes beyond the scope of the "NAS" purpose.
Now to who you set it up for, it can be considered at that point as an appliance. Edit: It's now serving as a specific purpose, and is now limiting their configuration ability.
But for you, it's not clear. Because you have the password, and can do what you want with hit. But who you set it up for and are supporting it for, different story.
-
I'm going back and forth from both sides here, maybe that isn't clear. I try to prove and disprove at the same time, as if I'm a fanatic of both sides, and see which one stands.
-
@Tim_G said in What Makes Something An Appliance:
@scottalanmiller said in What Makes Something An Appliance:
@Tim_G said in What Makes Something An Appliance:
@Tim_G said in What Makes Something An Appliance:
Or, limited due to design... as in it's just not possible.
By that, I mean not possible as it is. It may be possible by installing more software, packages, addons, etc... but that's not it's original purpose.
But what would be an example? All OSes require software added on to do things. The thing that makes something a general purpose OS is that you can run arbitrary code on it, not that it includes all potential functionality.
Well, lets say you download FreeNAS and set it up on a physical or virtual server. You configure it for it's original purpose, as and only as a NAS. Now you password it, so nobody can make any configuration changes beyond the scope of the "NAS" purpose.
Now to who you set it up for, it can be considered at that point as an appliance. Edit: It's now serving as a specific purpose, and is now limiting their configuration ability.
But for you, it's not clear. Because you have the password, and can do what you want with hit. But who you set it up for and are supporting it for, different story.
Right, and would apply equally to all servers in your environment.
What is a server to use is an appliance to the customer.
-
@Tim_G said in What Makes Something An Appliance:
I'm going back and forth from both sides here, maybe that isn't clear. I try to prove and disprove at the same time, as if I'm a fanatic of both sides, and see which one stands.
Same with me. I want something to be an appliance, but if we can't define it meaningfully, we shouldn't accept the definition.
-
Maybe we are looking at this all wrong. Maybe we are using the term "server" incorrectly and "appliance" should be the appropriate term for what we are trying to define.
Server is merely a service that supports clients. Typically it is just built with other servers within an OS.
-
I'm starting to come to the conclusion that in computing, we can't come up with a meaningful enough definition for appliance. We can't draw a line because depending on your view, the line can go anywhere, and be pushed around so easily depending on who using said 'appliance'. Technically, all computing appliances like FreeNAS, KACE, etc, are only limiting their configuration by a username and password. Does that even count? At that point, the person who has the username and password is no longer limited and therefore is not an appliance. Then it's just a server.
-
@NerdyDad said in What Makes Something An Appliance:
Maybe we are looking at this all wrong. Maybe we are using the term "server" incorrectly and "appliance" should be the appropriate term for what we are trying to define.
Server is merely a service that supports clients. Typically it is just built with other servers within an OS.
Maybe, that's definitely a thought. But okay, say we drop the term "server"... what do servers become?
-
@Tim_G said in What Makes Something An Appliance:
I'm starting to come to the conclusion that in computing, we can't come up with a meaningful enough definition for appliance. We can't draw a line because depending on your view, the line can go anywhere, and be pushed around so easily depending on who using said 'appliance'. Technically, all computing appliances like FreeNAS, KACE, etc, are only limiting their configuration by a username and password. Does that even count? At that point, the person who has the username and password is no longer limited and therefore is not an appliance. Then it's just a server.
FreeNAS doesn't even do that. Kace is one category of "thing", FreeNAS is another. Maybe both are appliances, or neither, but whatever they fall into, they at least fall into different sub-categories.
-
@scottalanmiller said in What Makes Something An Appliance:
@NerdyDad said in What Makes Something An Appliance:
Maybe we are looking at this all wrong. Maybe we are using the term "server" incorrectly and "appliance" should be the appropriate term for what we are trying to define.
Server is merely a service that supports clients. Typically it is just built with other servers within an OS.
Maybe, that's definitely a thought. But okay, say we drop the term "server"... what do servers become?
To me, a server is merely a service that runs on a device (computer, router, whatever) that supports other devices connected on a network. For example DHCP is a service, DNS is a service, etc.
-
Well and there is another thing to consider.... the thread that this came from, this question was triggered because a few people wanted to exclude "appliances" from their list of servers, even though they are the most "unlimited" form of appliances where there were no limits on usage at all, not license nor technology. So that was the trigger to "well we need a real definition then."
Maybe what we need is to accept that an appliance is a sub-category of server, not an alternative to a server. That might solve things.
But is a NetApp still a server? Argh.
-
@NerdyDad said in What Makes Something An Appliance:
@scottalanmiller said in What Makes Something An Appliance:
@NerdyDad said in What Makes Something An Appliance:
Maybe we are looking at this all wrong. Maybe we are using the term "server" incorrectly and "appliance" should be the appropriate term for what we are trying to define.
Server is merely a service that supports clients. Typically it is just built with other servers within an OS.
Maybe, that's definitely a thought. But okay, say we drop the term "server"... what do servers become?
To me, a server is merely a service that runs on a device (computer, router, whatever) that supports other devices connected on a network. For example DHCP is a service, DNS is a service, etc.
Right, that defines what a server is to you. But then how do you define the thing that we used to call a server? What will that become?
-
@scottalanmiller said in What Makes Something An Appliance:
@NerdyDad said in What Makes Something An Appliance:
@scottalanmiller said in What Makes Something An Appliance:
@NerdyDad said in What Makes Something An Appliance:
Maybe we are looking at this all wrong. Maybe we are using the term "server" incorrectly and "appliance" should be the appropriate term for what we are trying to define.
Server is merely a service that supports clients. Typically it is just built with other servers within an OS.
Maybe, that's definitely a thought. But okay, say we drop the term "server"... what do servers become?
To me, a server is merely a service that runs on a device (computer, router, whatever) that supports other devices connected on a network. For example DHCP is a service, DNS is a service, etc.
Right, that defines what a server is to you. But then how do you define the thing that we used to call a server? What will that become?
I think that would depend as to whether it was physical or virtual. Physical = Host, Virtual = Guest Machine or VM.
