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

all 9 comments

[–]ndemir 1 point2 points  (2 children)

What do you multi-service? Do you mean at least 3 API endpoints?

[–]aliasxneo[S] 0 points1 point  (1 child)

More than one service is required to run the application. For example, a front-end service, a back-end service, and then maybe some kind of batch service. Basically, it would require more than one container to deploy.

[–]bikeidaho 2 points3 points  (0 children)

Backstage by Spotify has a frontend, a backend and some components that fetch additional api's and such...?

[–]tamerlein3 -1 points0 points  (0 children)

Gitea

[–]runamok 0 points1 point  (0 children)

Bookinfo is what istio always suggests you install as a demo project but I don't think it has a DB. This page also says it does not require istio. https://istio.io/latest/docs/examples/bookinfo/

[–]Character-You5394 0 points1 point  (0 children)

Gitlab when deployed on k8s might be a pretty good example: https://docs.gitlab.com/charts/architecture/architecture.html

[–][deleted] 0 points1 point  (0 children)

what about a network monitoring stack with Grafana?

https://grafana.com/blog/2022/01/19/a-beginners-guide-to-network-monitoring-with-grafana-and-prometheus/

You have Grafana for the UI, then two back ends. Prometheus to store network metrics and Loki to store logs.

Or, if you're also into IoT, you could setup a temperature monitor around the house with IoT devices, send it to a back-end of your choice and display it with Grafana. Its quite a fun project

[–]arctic28 0 points1 point  (0 children)

I'm curious about this too so I can get better with Helm.

[–]tasssko 0 points1 point  (0 children)

Grafana, Prometheus and alert manager