Some extension ideas :) about go-micro-services HOT 2 CLOSED

@joeblew99 thanks for the note - totally agree that queues are an important part of microservice architecture. NSQ feels like a pretty solid choice here, and from my limited experience with it, seems like a great choice for applications that need to communicate in an async fashion.

Would be cool if you have any thoughts on this. I am happy to make a PR for this and contrib it back to this repo too. There are not enough examples of this around i feel.

Sounds good. Any ideas on functionality?

from go-micro-services.

thanks for the response :)

Can you comment on why your not using grpc-gateway.
It would get right a some of your boiler plate. I hate typing :)

• Easy to have a go at it too.
• You get a swagger API fro free too.
• Also grpc-web is ongong private repo, and so it will be easy to swap out when its ready later.

Now about the idea of putting in a Message queue layer and functionality:

• With a MQ, then all the good things of CQRS are then thee for the taking.
• Providence / Audit trail from the event store logs
• Ability to relay logs to simulate a bug or crash
• No need for DB migration scripts, because the event store is the full history. Its similar to how the blockchain works. When you change anything in the system just replay the logs back into the system and lets the read and write databases fill up. Its weir to get used to, but its there and makes doing advanced architectures such as machine learning possible for example.

Lbs that work well with your setup:
https://github.com/andrewwebber/cqrs

• Very well documented
• Clear

https://github.com/nvcnvn/nsq_to_couchbase

• Needed to store logs for every
• Couchbase is all golang and makes it easy to go HA.
• Your events will have Full facet search. Huge
• I woudl also pipe all application logs and metrics into it for pushing off to Prometheus later. Again the facet search is huge here because you get to have amazing tooling for search for free.
• I would even put tracing into it. But not sure yet.

Coach DB is a controversial choice for Message queue backing i know.
Couch has come along really well now and is 100% golang with offline support and full facet and text search integrated. Its compelling.
Its clear that Microservices shoudl use what they want, but i need to pick one DB as a basis for the infrastructure layer of the control plane. Hope you get me.

I dont think its a huge thing to adapt what you have now to start to use some of this.

from go-micro-services.