Xinhari provides the core requirements for distributed systems development including RPC and Event driven communication. The Xinhari philosophy is sane defaults with a pluggable architecture. We provide defaults to get you started quickly but everything can be easily swapped out.
Xinhari abstracts away the details of distributed systems. Here are the main features.
-
Authentication - Auth is built in as a first class citizen. Authentication and authorization enable secure zero trust networking by providing every service an identity and certificates. This additionally includes rule based access control.
-
Dynamic Config - Load and hot reload dynamic config from anywhere. The config interface provides a way to load application level config from any source such as env vars, file, etcd. You can merge the sources and even define fallbacks.
-
Data Storage - A simple data store interface to read, write and delete records. It includes support for memory, file and CockroachDB by default. State and persistence becomes a core requirement beyond prototyping and Xinhari looks to build that into the framework.
-
Service Discovery - Automatic service registration and name resolution. Service discovery is at the core of xinhari service development. When service A needs to speak to service B it needs the location of that service. The default discovery mechanism is multicast DNS (mdns), a zeroconf system.
-
Load Balancing - Client side load balancing built on service discovery. Once we have the addresses of any number of instances of a service we now need a way to decide which node to route to. We use random hashed load balancing to provide even distribution across the services and retry a different node if there's a problem.
-
Message Encoding - Dynamic message encoding based on content-type. The client and server will use codecs along with content-type to seamlessly encode and decode Go types for you. Any variety of messages could be encoded and sent from different clients. The client and server handle this by default. This includes protobuf and json by default.
-
gRPC Transport - gRPC based request/response with support for bidirectional streaming. We provide an abstraction for synchronous communication. A request made to a service will be automatically resolved, load balanced, dialled and streamed.
-
Async Messaging - PubSub is built in as a first class citizen for asynchronous communication and event driven architectures. Event notifications are a core pattern in xinhari service development. The default messaging system is a HTTP event message broker.
-
Synchronization - Distributed systems are often built in an eventually consistent manner. Support for distributed locking and leadership are built in as a Sync interface. When using an eventually consistent database or scheduling use the Sync interface.
-
Pluggable Interfaces - Xinhari makes use of Go interfaces for each distributed system abstraction. Because of this these interfaces are pluggable and allows Xinhari to be runtime agnostic. You can plugin any underlying technology. Find plugins in github.com/xinhari/plugins.
To make use of Xinhari
import "xinhari.com/xinhari"
// create a new service
service := xinhari.NewService(
xinhari.Name("com.exnamespace.srv.helloworld"),
)
// initialise flags
service.Init()
// start the service
service.Run()See the docs for detailed information on the architecture, installation and use of xinhari.
Thank you for considering contributing to the Xinhari framework! The contribution guide can be found in the Xinhari documentation.
Advanced development of Go Micro 2
Xinhari is Apache 2.0 licensed.
