Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/adalkiran/go-inventa
A Go library for microservice registry and executing RPC (Remote Procedure Call) over Redis.
https://github.com/adalkiran/go-inventa
cross-language cross-platform distributed-computing distributed-systems go golang-library microservices orchestration redis remote-procedure-calls rpc rpc-framework rpc-library service-discovery
Last synced: 3 months ago
JSON representation
A Go library for microservice registry and executing RPC (Remote Procedure Call) over Redis.
- Host: GitHub
- URL: https://github.com/adalkiran/go-inventa
- Owner: adalkiran
- License: apache-2.0
- Created: 2022-07-24T21:57:44.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2022-08-20T20:25:27.000Z (over 2 years ago)
- Last Synced: 2024-05-21T01:39:40.246Z (9 months ago)
- Topics: cross-language, cross-platform, distributed-computing, distributed-systems, go, golang-library, microservices, orchestration, redis, remote-procedure-calls, rpc, rpc-framework, rpc-library, service-discovery
- Language: Go
- Homepage:
- Size: 24.4 KB
- Stars: 4
- Watchers: 2
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# **Inventa for Go**
[](https://www.linkedin.com/in/alper-dalkiran/)
[](https://twitter.com/aalperdalkiran)
A Go library for microservice registry and executing RPC (Remote Procedure Call) over Redis.
## **WHY THIS PROJECT?**
Service discovery, registry, and execution of remote procedures are some of the necessary tools in distributed applications. You must track which services (also how many replica instances of them) are alive. Also, your services should communicate between each other (choreography) or via an orchestrator service on top of them.
You can do API/function calls remotely by serving REST APIs, gRPC endpoints, etc... But these choices came with some drawbacks or advantages, you have lots of different architectural options on this topic.
Inventa offers you a lightweight solution for these requirements; if you already have Redis in your project's toolbox, and if all of your services have access to this Redis instance.
Also, Inventa doesn't abstract/hide its Redis client object, you can use its Redis Client object freely which is already connected to the server.
## **USAGE SCENARIO**
* You have an application that consists of multiple services, developed with different languages (currently [Go](https://github.com/adalkiran/go-inventa) and [Python](https://github.com/adalkiran/py-inventa) are supported),
* These services exist for different jobs, also they may be replicated into more than one instances, may be run in either different containers or machines,
* There is one registrar/orchestrator service which other services will register themselves and send their heartbeats to it,
* The orchestrator knows which service types and instances are alive now, the orchestrator should select one of the instances of a specific service, then call a function/procedure of the service, and get a response remotely.
* All of your services will use Inventa, the one orchestrator service will instantiate it in **Orchestrator** Inventa role, other services will instantiate it in **Service** Inventa role.
* Both Service roles and the Orchestrator role can call functions that are provided by other services if they know target service's identifier.
## **INSTALLATION**
```sh
go get github.com/adalkiran/go-inventa
```
## **EXAMPLE PROJECT**
You can find example projects made using Inventa at [https://github.com/adalkiran/inventa-examples](https://github.com/adalkiran/inventa-examples).
## **OTHER IMPLEMENTATIONS**
You can find Python implementation of Inventa on [Inventa for Python (py-inventa)](https://github.com/adalkiran/py-inventa).
## **LICENSE**
Inventa for Go is licensed under the Apache License, Version 2.0. See [LICENSE](LICENSE) for the full license text.