elasticsearch_exporter
Go-CQRS-EventSourcing-Microservice
Our great sponsors
| elasticsearch_exporter | Go-CQRS-EventSourcing-Microservice | |
|---|---|---|
| 2 | 1 | |
| 1,851 | 86 | |
| 1.3% | - | |
| 8.2 | 0.0 | |
| 5 days ago | almost 2 years ago | |
| Go | Go | |
| Apache License 2.0 | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
elasticsearch_exporter
-
Incorrect document count displayed
After the dependent application is finally optimized for Elasticsearch version 7, the cluster was updated from version 6.8.8 to 7.10.1. The cluster is running inside K8S and is managed by the latest version (2.1.0) of the Elastic operator, and monitored by prometheus-community/elasticsearch_exporter also on the latest 1.3.0 version.
-
Monitoring Shard Allocation In OpenSearch
I've done similar things with the elasticsearch_exporter. It's helped debug scaling problems for us.
Go-CQRS-EventSourcing-Microservice
-
Go EventSourcing and CQRS with PostgreSQL, Kafka, MongoDB and ElasticSearch 👋✨💫
Source code you can find in GitHub repository. The main idea of this project is the implementation of Event Sourcing and CQRS using Go, Postgresql, Kafka for event store and Mongo, ElasticSearch for read projections. Previously have written same articles where implemented the same microservice using Go and EventStoreDB, and Spring, as written before, repeat, think EventStoreDB is the best choice for event sourcing, but in real life at some projects we usually have business restrictions and for example usage of the EventStoreDB can be not allowed, in this case, think postgres and kafka is good alternative for implementing our own event store. If you don't familiar with EventSourcing and CQRS patterns, the best place to read is microservices.io, blog and documentation of eventstore site is very good too, and highly recommend Alexey Zimarev "Hands-on Domain-Driven Design with .NET Core" book.
What are some alternatives?
Grafana - The open and composable observability and data visualization platform. Visualize metrics, logs, and traces from multiple sources like Prometheus, Loki, Elasticsearch, InfluxDB, Postgres and many more.
grpc-go - The Go language implementation of gRPC. HTTP/2 based RPC
goes - goes is an event-sourcing framework for Go.
validator - :100:Go Struct and Field validation, including Cross Field, Cross Struct, Map, Slice and Array diving
pdash - orders dashboard in microservices architecture
jaeger - CNCF Jaeger, a Distributed Tracing Platform
kafka-go - Kafka library in Go
shop-golang-microservices - Practical microservices based on different software architecture and technologies like Golang, CQRS, Vertical Slice Architecture, Docker, RabbitMQ, OpenTelemetry, Postgresql, ...
bloomrpc - Former GUI client for gRPC services. No longer maintained.
ddd-hexagonal-cqrs-es-eda - Complete working example of using Domain Driven Design (DDD), Hexagonal Architecture, CQRS, Event Sourcing (ES), Event Driven Architecture (EDA), Behaviour Driven Development (BDD) using TypeScript and NestJS. Like what you see? Don't forget to star! ⭐ ^^^
pgx - PostgreSQL driver and toolkit for Go