Kubernetes notes (4)--application VS Service

This is a creation in Article, where the information may have evolved or changed.

A service is a process, that:
1. is designed to do a small number of things (often just one).
2. Have no user interface and is invoked solely via some kind of APIs.
An application, on the other hand, was pretty much the opposite of that. It has a user interface (even if it's just a command line) and often performs lots of different tasks. It can also expose an API, but that ' s just bonus points.

Personal understanding, service generally focused on doing one thing, no user interface, and API through application interacting with. applicationThere is a user interface, and you can usually run many tasks. As an example, that is, and that is web browser application web server service .

A Kubernetes cluster does not manage a fleet of applications. It manages a cluster of services. A service running in a container managed by Kubernetes are designed to do a very small number of discrete things.

If your services is small and of limited purpose, then they can + easily be scheduled and re-arranged as your load dem ANDs. Otherwise, the dependencies become too much to manage and either your scale or your stability suffers.

K8sThat is used for management service .