I'm not sure there's anything go-specific other than libraries and
frameworks; just general good practices. One of the best things I can
recommend to keep microservices from becoming a mess is to treat every
service like it's external:
- Have a well-defined, versioned API contract for each servi
Thanks Nyah! But that's a framework for developing microservices and I'm
already using one; NATS (although it's more low level).
What I'm looking for is the "development tools"/process/practices that
helps in the "process of developing" (not designing or implementing) a
microservices architectu
This should help: https://github.com/micro
On Thu, Feb 23, 2017 at 2:17 PM, dc0d wrote:
> How do you develop a microservice based (architecture) app? I have some
> scripts that are doing the building, starting and stopping and also running
> tests. But do you use any specific tools for developin
How do you develop a microservice based (architecture) app? I have some
scripts that are doing the building, starting and stopping and also running
tests. But do you use any specific tools for developing microservices?
- Env: Apps are communicating via NATS (& some HTTP), Go 1.8, Ubuntu 14.04
(
