wtf is go-micro-stack?

go-micro-stack is a reference project showing how to build an event driven set of microservices in Go with the kind of infrastructure a real production system would need. Instead of one big application, it is split into small services that talk to each other indirectly through an event log rather than calling one another directly. Requests come in through KrakenD, which acts as the single front door, or API gateway, routing traffic to the right service and passing along tracing information so requests can be followed across the whole system. An order service receives requests to create orders, checks Redis to make sure the same request is not processed twice, saves the order to a PostgreSQL database, and then publishes an event about the new order to Apache Kafka, a message broker that other services can subscribe to. A separate notification service listens for those Kafka events and logs that a notification would be sent. Secrets like database passwords and API keys are kept out of the code and stored in HashiCorp Vault, a dedicated secrets manager, rather than sitting in configuration files. On the observability side, the project wires up the full LGTM stack: Grafana for dashboards, Loki for logs, Tempo for distributed traces, and Prometheus for metrics, all fed through the OpenTelemetry collector so every service's traces, metrics, and logs end up visualized in one place. Each piece of infrastructure uses persistent storage rather than memory alone: Kafka topics, the Postgres database, Redis's cache, and Vault's secret store are all written to disk or object storage so data survives a restart. The project includes a full local setup meant to be run end to end with the included configuration files for each component, from the API gateway down to the monitoring stack. This is a Go project intended as a hands-on example of production style microservice patterns rather than a single deployable product.