Explore the docs »
View Demo
·
Report Bug
·
Request Feature
GO-KIT is one of the popular toolkit for building microservices in GO. It does a lot of heavy lifting when you get started.
Go-Kit is opinionated in the way you need to structure your microservices (transport layer, endpoint layer and service layer) which ensures a common standard among the development teams.
Out of the box, you are getting different integrations to tracing, logging, transporting, service discovery and metrics.
Yet, while working with Go-Kit, I found there are still missing important concepts, such as:
- configuration management
- transporting context between microservices
- working with databases
- handling execution fallbacks
- working with errors
Corego tries to be more opinionated and focus on selected integrations:
- consul and coreDNS for service discovery
- consul as remote KV
- zap as logger
- prometheos and datadog for metrics
- zipkin for tracing
- cassandra, elastic, mongo for databases
- rabbit for amqp transport
GO-KIT-USER-MS-EXAMPLE repo uses corego as an engine to create and run a real world microservice example
See the open issues for a list of proposed features (and known issues).
Contributions are what make the open source community such an amazing place to be learn, inspire, and create. Any contributions you make are greatly appreciated.
- Fork the Project
- Create your Feature Branch (
git checkout -b feature/AmazingFeature
) - Commit your Changes (
git commit -m 'Add some AmazingFeature'
) - Push to the Branch (
git push origin feature/AmazingFeature
) - Open a Pull Request
Distributed under the MIT License. See LICENSE
for more information.
Guy Kolbis - @GKolbis - guyk@net-bet.net
Project Link: https://github.com/kolbis/corego