The above article gave an example of a To-do app for the simplicity of explanation.
I would imagine that any workload run on Kubernetes adheres at least in some way to a "connected" service architecture. While this could be something as simple as a program that takes some input X and produces output Y, using Kubernetes at the very least might provide you with the benefit of horizontal scalability.
As mentioned in one of the replies by Fernandino Silva, not every workload requires Kubernets. Running a standalone desktop application probably wouldn't need a whole cluster behind itself. It's back-end infrastructure on the other hand could very well be deployed via Kubernetes, especially in the case where the front-end app is just one of many clients.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The above article gave an example of a To-do app for the simplicity of explanation.
I would imagine that any workload run on Kubernetes adheres at least in some way to a "connected" service architecture. While this could be something as simple as a program that takes some input X and produces output Y, using Kubernetes at the very least might provide you with the benefit of horizontal scalability.
As mentioned in one of the replies by Fernandino Silva, not every workload requires Kubernets. Running a standalone desktop application probably wouldn't need a whole cluster behind itself. It's back-end infrastructure on the other hand could very well be deployed via Kubernetes, especially in the case where the front-end app is just one of many clients.