Go-CQRS-EventSourcing-Microservice VS bloomrpc

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.

Why another one? I'm working with gRPC every day and for my opinion all existed GUI clients do not well designed or do not have fully gRPC features support. And some of them like BloomRPC unfortunately are unmaintained.

There’s also BloomRPC, which is like Postman/Insomnia for GRPC:

https://github.com/bloomrpc/bloomrpc

Can recommend bloomrpc is good GUI Client for GRPC Services. Grpc service handlers:

I would like to introduce you to a gRPC client tool(pgt) for your own use, it is used similarly to postman/bloomrpc.

Hey! Not at all. There is a wonderful tool called BloomRPC I mainly use this. Very recently Postman announced that they will support gRPC too. Postman Blog

The best alternative I found is BloomRPC

You can also play with the gRPC API, the nicest interface I found was Bloomrpc. Have fun!