Go Micro is a framework for distributed systems development

Overview

Go Micro License Go.Dev reference Travis CI Go Report Card

Go Micro is a framework for distributed systems development.

Overview

Go Micro provides the core requirements for distributed systems development including RPC and Event driven communication. The Micro philosophy is sane defaults with a pluggable architecture. We provide defaults to get you started quickly but everything can be easily swapped out.

Features

Go Micro 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 Micro looks to build that into the framework.

  • Service Discovery - Automatic service registration and name resolution. Service discovery is at the core of micro 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.

  • RPC Client/Server - RPC 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 micro 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 - Go Micro makes use of Go interfaces for each distributed system abstraction. Because of this these interfaces are pluggable and allows Go Micro to be runtime agnostic. You can plugin any underlying technology.

Getting Started

To make use of Go Micro

import "github.com/asim/go-micro/v3"

// create a new service
service := micro.NewService(
    micro.Name("helloworld"),
)

// initialise flags
service.Init()

// start the service
service.Run()

See the docs for detailed information on the architecture, installation and use of go-micro.

Code Generation

See cmd/protoc-gen-micro for protobuf code generation.

Example Usage

See examples directory for usage examples.

Plugins

See plugins directory for all the plugins.

License

Go Micro is Apache 2.0 licensed.

Upgrade

Micro v3 consolidates Go Micro into it as a single unified platform. Please see the upgrade guide.

Issues
  • example of compose two or more services with single binary

    example of compose two or more services with single binary

    I like go-micro design, but if i want to provide single binary with all my services together. For example that implements some api with 10 different services. How can i do that with go-micro? All this services need to communicate via message bus (nats or etcd).

    opened by vtolstov 23
  • RPC stream client/server mutex fix

    RPC stream client/server mutex fix

    As described in #878 (and #532) it is not possible to send messages while waiting to receive them as well (or vice-versa), due to RPC stream client and server being locked by both Send() and Recv() functions.

    In order to solve this issue, I unlock the Mutex before calling the codec to receive data, and locking it again after codec returned. This way we still have the Mutex protection of the client/server structs, but we can send/receive at same time.

    :warning: Note that this assumes that codec does not need protection while being active.

    I did not update Send() because I assumed that it won't block. By only fixing Recv() the Send() worked as welll. Maybe depending on transport/codec it can block as well?

    I only considered these 2 components/files, as we are (currently) not having issues in other parts of the go-micro framework regarding to this. If needed I can update other parts as well to stay in sync with this change.

    I have tested this in our micro-service environment and it all seems to work fine. I did not trigger race conditions or other panics. But I did not yet perform (high) load or long running tests, which would make race conditions more likely to pop up (if there are any).

    enhancement WIP RPC 
    opened by veger 22
  • build command-line-arguments: cannot load crypto/ed25519: cannot find module providing package crypto/ed2551

    build command-line-arguments: cannot load crypto/ed25519: cannot find module providing package crypto/ed2551

    When I run the go-micro,it tips build command-line-arguments: cannot load crypto/ed25519: cannot find module providing package crypto/ed25519,but i find the module is exists in gopath.

    question more info requsted go.mod 
    opened by songdony 20
  • consul registry broken: mismatch in type due to import being expected from

    consul registry broken: mismatch in type due to import being expected from "github.com/hashicorp/consul/vendor"

    My Go version is 1.12.5.

    I'm building my package binary using the golang1.12.5-alpine3.9 Docker image as a package builder and I'm running the following commands in my Dockerfile to install all the necessary dependencies -

    # install source dependencies
    RUN go get -d -v ./...
    RUN go install -v ./...
    

    the go get command works as expected but the go install command crashes with an exit code: 2 and the following message -

    # github.com/micro/go-micro/registry/consul /go/src/github.com/micro/go-micro/registry/consul/watcher.go:48:33: cannot use cr.Client (type *"github.com/hashicorp/consul/api".Client) as type *"github.com/hashicorp/consul/vendor/github.com/hashicorp/consul/api".Client in argument to wp.RunWithClientAndLogger /go/src/github.com/micro/go-micro/registry/consul/watcher.go:213:37: cannot use cw.r.Client (type *"github.com/hashicorp/consul/api".Client) as type *"github.com/hashicorp/consul/vendor/github.com/hashicorp/consul/api".Client in argument to wp.RunWithClientAndLogger

    Just FYI, I was able to generate the Docker based package builder successfully up till 3 days ago.

    opened by desertjinn 20
  • gossip registry

    gossip registry

    I'm experiment with gossip registry and may be found some specific issue. When i'm start first service1 with specify gossip.Address("172.16.1.254:4223") and on other server service2 with registry.Addrs("172.16.1.254:4223") and gossip.Address("172.16.1.1:0")

    i see that members equal 2 on both sides, but the second service does not registered in registry. But if i stop service1 and start it with registry.Addrs("172.16.1.254:4223") and gossip.Address("172.16.1.1:xxx") where xxx is port provided by service2 all works fine. So issue appears only on first service1 when it start first without other members.

    opened by vtolstov 20
  • [BUG] Micro API fails on streaming endpoint unexpected nil error

    [BUG] Micro API fails on streaming endpoint unexpected nil error

    Describe the bug

    1. What are you trying to do? Run micro api gateway and call a streaming endpoint
    2. What did you expect to happen? Success, actual response
    3. What happens instead?
    {
        "code": 500,
        "detail": "grpc: client streaming protocol violation: get <nil>, want <EOF>",
        "id": "go.micro.client",
        "status": "Internal Server Error"
    }
    

    How to reproduce the bug: micro version 2.0.0 micro api --address :8085 --namespace some.ns --handler rpc http localhost:8085/my/streaming/endpoint

    If possible, please include a minimal code snippet here.

           ctx, cancel := context.WithCancel(ctx)
    	ch, errCh := data.GetSomeData(ctx, cancel, s.db, s.service)
    
    	for {
    		select {
    		case <-ctx.Done():
    			stream.Close()
    			return nil
    		case err := <-errCh:
    			return err
    		case msg := <-ch:
    			if msg == nil {
    				return nil
    			}
    			err := stream.Send(msg)
    			if err != nil {
    				cancel()
    				for len(ch) > 0 {
    					<-ch
    				}
    				return errors.InternalServerError(s.service.Name(), err.Error())
    			}
    		}
    	}
    

    Environment: Go Version: please paste go version output here

    go version go1.13.1 darwin/amd64
    
    opened by OGKevin 17
  • Disable timeout on RPC stream connection

    Disable timeout on RPC stream connection

    For a stream RPC connection I'd like to get rid of timeout, I see/found two solutions:

    1. Set timeout to some huge value and hope the client never stays connected long enough.
    2. Set timeout to -1 which 'somehow' seems to work. (Actually strconv.ParseUint() chokes on it and context timeout is not set (and no error is issued...))

    Both options feel hacky to me... Is there a better/recommended solution instead?

    enhancement 
    opened by veger 17
  • go get -u fails, apparently due to coreos/etcd move

    go get -u fails, apparently due to coreos/etcd move

    Go version: go1.13 Problem: when I run go get -u github.com/micro/go-micro I get the following error:

    # github.com/coreos/etcd/clientv3
    src/github.com/coreos/etcd/clientv3/auth.go:121:72: cannot use auth.callOpts (type []"github.com/coreos/etcd/vendor/google.golang.org/grpc".CallOption) as type []"go.etcd.io/etcd/vendor/google.golang.org/grpc".CallOption in argument to auth.remote.AuthEnable
    src/github.com/coreos/etcd/clientv3/auth.go:126:74: cannot use auth.callOpts (type []"github.com/coreos/etcd/vendor/google.golang.org/grpc".CallOption) as type []"go.etcd.io/etcd/vendor/google.golang.org/grpc".CallOption in argument to auth.remote.AuthDisable
    src/github.com/coreos/etcd/clientv3/auth.go:131:152: cannot use auth.callOpts (type []"github.com/coreos/etcd/vendor/google.golang.org/grpc".CallOption) as type []"go.etcd.io/etcd/vendor/google.golang.org/grpc".CallOption in argument to auth.remote.UserAdd
    src/github.com/coreos/etcd/clientv3/auth.go:136:144: cannot use auth.callOpts (type []"github.com/coreos/etcd/vendor/google.golang.org/grpc".CallOption) as type []"go.etcd.io/etcd/vendor/google.golang.org/grpc".CallOption in argument to auth.remote.UserAdd
    src/github.com/coreos/etcd/clientv3/auth.go:141:86: cannot use auth.callOpts (type []"github.com/coreos/etcd/vendor/google.golang.org/grpc".CallOption) as type []"go.etcd.io/etcd/vendor/google.golang.org/grpc".CallOption in argument to auth.remote.UserDelete
    src/github.com/coreos/etcd/clientv3/auth.go:146:122: cannot use auth.callOpts (type []"github.com/coreos/etcd/vendor/google.golang.org/grpc".CallOption) as type []"go.etcd.io/etcd/vendor/google.golang.org/grpc".CallOption in argument to auth.remote.UserChangePassword
    src/github.com/coreos/etcd/clientv3/auth.go:151:104: cannot use auth.callOpts (type []"github.com/coreos/etcd/vendor/google.golang.org/grpc".CallOption) as type []"go.etcd.io/etcd/vendor/google.golang.org/grpc".CallOption in argument to auth.remote.UserGrantRole
    src/github.com/coreos/etcd/clientv3/auth.go:156:80: cannot use auth.callOpts (type []"github.com/coreos/etcd/vendor/google.golang.org/grpc".CallOption) as type []"go.etcd.io/etcd/vendor/google.golang.org/grpc".CallOption in argument to auth.remote.UserGet
    src/github.com/coreos/etcd/clientv3/auth.go:161:72: cannot use auth.callOpts (type []"github.com/coreos/etcd/vendor/google.golang.org/grpc".CallOption) as type []"go.etcd.io/etcd/vendor/google.golang.org/grpc".CallOption in argument to auth.remote.UserList
    src/github.com/coreos/etcd/clientv3/auth.go:166:106: cannot use auth.callOpts (type []"github.com/coreos/etcd/vendor/google.golang.org/grpc".CallOption) as type []"go.etcd.io/etcd/vendor/google.golang.org/grpc".CallOption in argument to auth.remote.UserRevokeRole
    src/github.com/coreos/etcd/clientv3/auth.go:166:106: too many errors
    

    We first saw this error when our CI build began to fail, and at first couldn't reproduce it locally, but then were able to by adding the -u to the command. Alternately, here's a simple Dockerfile that demonstrates the issue when building it.

    This seems to be caused by the moving of github.com/coreos/etcd to github.com/etcd-io/etcd, as described here: https://github.com/etcd-io/etcd/pull/10044#issuecomment-417125341

    That change and the issue are from last year, so I'm not sure why this is just showing up now, but my colleagues and I (and our CI) can all reproduce the problem now.

    I will look into creating a PR that changes the imports from coreos/etcd to etcd-io/etcd.

    go.mod 
    opened by newrelic-eheinlein 17
  • Adding TLS to RPC

    Adding TLS to RPC

    I'm feeling a little bit dumb, I don't suppose you have an example of adding TLS to a RPC service?

    	security.Setup(log, security.Vault())
    	tlsConfig := &tls.Config{
    		GetCertificate: security.Vault().CertificateGetter(),
    	}
    
    	// initialise service
    	service.Init(
    		micro.Action(func(c *cli.Context) {
    			if c.Bool("debug") {
    				log.Level = logrus.DebugLevel
    				log.Debug("Debug log level enabled")
    			}
    		}),
    // transport.TLSConfig(tlsConfig),
    	)
    
    	countryHandler, err := handler.NewCountryHandler()
    	if err != nil {
    		log.Fatal(err)
    	}
    
    	country.RegisterCountriesHandler(service.Server(), countryHandler)
    
    	if err := service.Run(); err != nil {
    		log.Fatal(err)
    	}
    

    I tried adding transport options to the service.Init but it's clearly not that simple?

    opened by freman 17
  • Documentation unavailable : not displayed due to license restrictions

    Documentation unavailable : not displayed due to license restrictions

    Hello,

    This is not a #1956 or #1953 duplicate. :)

    I tried to access : https://pkg.go.dev/github.com/micro/go-micro/v3?tab=overview But the documentation is unavailable due to license restrictions.

    Thanks,

    opened by scorsi 15
  • [bug]go get -u github.com/micro/go-micro errors (maybe not update frequency)

    [bug]go get -u github.com/micro/go-micro errors (maybe not update frequency)

    ➜  ~ go get -u github.com/micro/go-micro
    
    # cd /home/glenlau/GoWork/src/github.com/marten-seemann/qtls; git pull --ff-only
    fatal: refusing to merge unrelated histories
    package github.com/marten-seemann/qtls: exit status 128
    
    question go.mod 
    opened by DuckulaGL 15
  • [BUG] Panic during receiving events occurs

    [BUG] Panic during receiving events occurs

    Describe the bug

    1. What are you trying to do? I'm trying to use pubsub pattern with default broker. v4.7.0

    2. What did you expect to happen? Successful publishing and receiving events

    3. What happens instead?

    2022-06-21 14:45:59 file=server/rpc_router.go:513 level=error goroutine 84 [running]: runtime/debug.Stack() /usr/lib/go/src/runtime/debug/stack.go:24 +0x65 go-micro.dev/v4/server.(*router).ProcessMessage.func1() /home/racoon/go/pkg/mod/go-micro.dev/[email protected]/server/rpc_router.go:513 +0xc5 panic({0xf79dc0, 0x11f8aa0}) /usr/lib/go/src/runtime/panic.go:844 +0x258 reflect.Value.Addr({0x10544a0?, 0xc000290ff0?, 0xc0002f6348?}) /usr/lib/go/src/reflect/value.go:273 +0x65 go-micro.dev/v4/server.(*router).ProcessMessage(0xc0001c0ab0, {0x12007a0, 0xc000290fc0}, {0x1202570?, 0xc000632480}) /home/racoon/go/pkg/mod/go-micro.dev/[email protected]/server/rpc_router.go:560 +0x553 go-micro.dev/v4/server.(*rpcServer).HandleEvent(0xc00017c780, {0x1200ce0?, 0xc000290f60?}) /home/racoon/go/pkg/mod/go-micro.dev/[email protected]/server/rpc_server.go:129 +0x47a go-micro.dev/v4/broker.(*httpBroker).ServeHTTP(0xc0001fc0f0, {0x11ffd58, 0xc00029e540}, 0xc000220400) /home/racoon/go/pkg/mod/go-micro.dev/[email protected]/broker/http.go:345 +0xab5 net/http.(*ServeMux).ServeHTTP(0xc00001c147?, {0x11ffd58, 0xc00029e540}, 0xc000220400) /usr/lib/go/src/net/http/server.go:2462 +0x149 net/http.serverHandler.ServeHTTP({0x11fdbf8?}, {0x11ffd58, 0xc00029e540}, 0xc000220400) /usr/lib/go/src/net/http/server.go:2916 +0x43b net/http.(*conn).serve(0xc0005300a0, {0x12007a0, 0xc000290120}) /usr/lib/go/src/net/http/server.go:1966 +0x5d7 created by net/http.(*Server).Serve /usr/lib/go/src/net/http/server.go:3071 +0x4db

    How to reproduce the bug:

    just run simple example with the newest go-micro version

    Environment: go version go1.18.3 linux/amd64

    GO111MODULE=""
    GOARCH="amd64"
    GOBIN=""
    GOCACHE="/home/racoon/.cache/go-build"
    GOENV="/home/racoon/.config/go/env"
    GOEXE=""
    GOEXPERIMENT=""
    GOFLAGS=""
    GOHOSTARCH="amd64"
    GOHOSTOS="linux"
    GOMODCACHE="/home/racoon/go/pkg/mod"
    GOOS="linux"
    GOPATH="/home/racoon/go"
    GOPROXY="https://proxy.golang.org,direct"
    GOROOT="/usr/lib/go"
    GOSUMDB="sum.golang.org"
    GOTMPDIR=""
    GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
    GOVCS=""
    GOVERSION="go1.18.3"
    GCCGO="gccgo"
    GOAMD64="v1"
    AR="ar"
    CC="gcc"
    CXX="g++"
    CGO_ENABLED="1"
    GOMOD="/home/racoon/develop/racoon-devel/examples/go.mod"
    GOWORK=""
    CGO_CFLAGS="-g -O2"
    CGO_CPPFLAGS=""
    CGO_CXXFLAGS="-g -O2"
    CGO_FFLAGS="-g -O2"
    CGO_LDFLAGS="-g -O2"
    PKG_CONFIG="pkg-config"
    GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build2203251113=/tmp/go-build -gno-record-gcc-switches"
    
    opened by racoon-devel 9
  • How to run api gateway at v4?

    How to run api gateway at v4?

    I'm trying to upgrade go-micro from v2 to v4 and stuck at api gateway at go-micro version 2, the code of api gateway

    main.go

    package main
    
    import (
    	"os"
    
    	"github.com/micro/go-micro/v2"
    	"github.com/micro/go-plugins/registry/kubernetes/v2"
    	"github.com/micro/micro/v2/cmd"
    )
    
    func main() {
    	configs := make([]micro.Option, 0)
    	if os.Getenv("MICRO_REGISTRY") == "kubernetes" {
    		configs = append(configs, micro.Registry(kubernetes.NewRegistry()))
    	}
    	cmd.Init(configs...)
    }
    
    

    plugin.go

    package main
    
    import (
    	"github.com/micro/go-plugins/micro/cors/v2"
    	_ "github.com/micro/go-plugins/registry/consul/v2"
    	"github.com/micro/micro/v2/client/api"
    )
    
    func init() {
    	api.Register(cors.NewPlugin())
    }
    
    

    and run like this

    MICRO_SERVER_NAME='local.test.grpc.gateway' MICRO_CLIENT=grpc MICRO_SERVER=grpc go run main.go plugin.go \
    	--registry=consul api \
    	--namespace='local.test.grpc' \
    	--cors-allowed-origins=* \
    	--cors-allowed-methods=POST,GET,PUT,DELETE \
    	--enable_rpc=true --address=0.0.0.0:8080
    
    

    but now i don't know how to run api gateway at version 4 and if i try to call api to service version 4 at api-gateway version 2 it's show error

    {"id":"go.micro.client","code":500,"detail":"stream terminated by RST_STREAM with error code: PROTOCOL_ERROR","status":"Internal Server Error"}
    

    please someone help me

    opened by ivybridge-3c33 1
  • [BUG] etcd plugin errors out on new project

    [BUG] etcd plugin errors out on new project

    Describe the bug

    1. What are you trying to do? I'm trying to use go-micro with the etcd registry
    2. What did you expect to happen? I expected the etcd plugin to be bundled with go-micro. I also expected it to work after pulling it in from the plugins explicitly.
    3. What happens instead? The error below

    How to reproduce the bug:

    If possible, please include a minimal code snippet here.

    $ micro new service my_service
    $ make proto update tidy
    $ cd my_service
    $ go run *.go --registry etcd
    Registry etcd not found
    exit status 1
    $ go get github.com/asim/go-micro/plugins/registry/etcd/v4
    <add to plugins.go>
    $ go run *.go --registry etcd
    # go.etcd.io/etcd/client/v3
    ../../go/pkg/mod/go.etcd.io/etcd/client/[email protected]/client.go:251:28: undefined: grpc.WithResolvers
    ../../go/pkg/mod/go.etcd.io/etcd/client/[email protected]/client.go:276:29: undefined: grpc.WithResolvers
    

    Environment: Go Version: please paste go version output here

    go version go1.18.1 darwin/arm64
    
    opened by jtweaver 1
  • [BUG] New service with jaeger failing for declared path - CLI

    [BUG] New service with jaeger failing for declared path - CLI

    Describe the bug

    1. What are you trying to do?
    micro new service --jaeger my_service
    make proto update tidy
    
    1. What did you expect to happen? Dependencies to be pulled correctly
    2. What happens instead?
    go: go-micro.dev/v4/cmd/micro/debug/trace/[email protected]: parsing go.mod:
    	module declares its path as: github.com/micro/go-micro
    	        but was required as: go-micro.dev/v4/cmd/micro/debug/trace/jaeger
    make: *** [update] Error 1
    

    How to reproduce the bug:

    If possible, please include a minimal code snippet here.

    micro new service --jaeger my_service
    cd my_service
    make proto update tidy
    

    Environment: Go Version: please paste go version output here go version go1.18.1 darwin/arm64

    opened by jtweaver 2
  • micro service reg consul by extranet ip

    micro service reg consul by extranet ip

    I have two micro services deployed on different pc, the two services reg the same consul by extranet ip. However, the second service can't access to first service by rpc.

    consul start-up: consul agent -server -ui -bootstrap-expect=1 -data-dir=/data/consul -node=hostname -bind=0.0.0.0 -advertise=49.234.57.x -client=0.0.0.0

    first service(go-micro-v3):

    func main() {
        service := micro.NewService(
            micro.Name("first"),
            micro.Registry(consul.NewRegistry(registry.Addrs("49.234.57.x:8500"))),
        )
        service.Init()
        pb.RegisterFirstHandler(service.Server(), new(handler.First))
        service.Run()
    }
    

    second service(go-micro-v3):

    func main() {
        service := micro.NewService(
            micro.Name("second"),
            micro.Registry(consul.NewRegistry(registry.Addrs("49.234.57.x:8500"))),
        )
        service.Init()
        firstCli := pb.NewFirstService("first", service.Client())
        go func() {
            time.Sleep(1*time.Second)
            obj := &pb.Response{}
            data, err := firstCli.Hello(context.Background(), &pb.Request{})
            if err != nil {
                 fmt.Println(err)
            } else {
                types.UnmarshalAny(data.GetData(), obj)
                fmt.Println(obj)
            }
        }
        service.Run()
    }
    

    Test:

    1. If the first/second server deployed on the same cloud pc, the second server can get data from the first server by rpc.
    2. If the first/second server deployed on different cloud pc(Both pc have access to all ports), I will get error: {"id":"go.micro.client","code":408,"detail":"call timeout: context deadline exceeded","status":"Request Timeout"}","time":"x"}

    the second service(ip: 52.81.x.x) can get data from the first server(ip: 49.234.57.x) by extranet ip reg consul?

    opened by hzxgo 0
  • Why go-micro using alot of ESTABLISHED connection

    Why go-micro using alot of ESTABLISHED connection

    Hi, Mr. @asim and go-micro developers Last week I got a problem with the consul down because of port limit config in consul then we have to check back on service and we saw go-micro using too many ESTABLISHED ports connect to the consul and won't connect and now we change to use k8s instead consul but still same problem

    example ports opening on services

    ~ # netstat -alpt
    Active Internet connections (servers and established)
    Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
    tcp        0      0 :::http-alt             :::*                    LISTEN      1/app
    tcp        0      0 :::35207                :::*                    LISTEN      1/app
    tcp        0      0 test-srv-74bc9c9c45-4ghnk:35207 10-1-1-109.api-geteway-srv.ft-poc.svc.cluster.local:42148 ESTABLISHED 1/app
    tcp        0      0 test-srv-74bc9c9c45-4ghnk:35207 10-1-1-109.api-geteway-srv.ft-poc.svc.cluster.local:42152 ESTABLISHED 1/app
    tcp        0      0 test-srv-74bc9c9c45-4ghnk:35207 10-1-1-109.api-geteway-srv.ft-poc.svc.cluster.local:42142 ESTABLISHED 1/app
    tcp        0      0 test-srv-74bc9c9c45-4ghnk:35207 10-1-1-109.api-geteway-srv.ft-poc.svc.cluster.local:42156 ESTABLISHED 1/app
    tcp        0      0 test-srv-74bc9c9c45-4ghnk:35207 10-1-1-109.api-geteway-srv.ft-poc.svc.cluster.local:42160 ESTABLISHED 1/app
    tcp        0      0 test-srv-74bc9c9c45-4ghnk:35207 10-1-1-109.api-geteway-srv.ft-poc.svc.cluster.local:42150 ESTABLISHED 1/app
    tcp        0      0 test-srv-74bc9c9c45-4ghnk:35207 10-1-1-109.api-geteway-srv.ft-poc.svc.cluster.local:42162 ESTABLISHED 1/app
    tcp        0      0 test-srv-74bc9c9c45-4ghnk:35207 10-1-1-109.api-geteway-srv.ft-poc.svc.cluster.local:42154 ESTABLISHED 1/app
    

    Can you explain why happen like this and how to fix this?

    ps. I'm using go-micro version 2.9.1

    Thank you very much.

    opened by ivybridge-3c33 0
Releases(v4.7.0)
Owner
Asim Aslam
Working on Micro
Asim Aslam
Distributed-Services - Distributed Systems with Golang to consequently build a fully-fletched distributed service

Distributed-Services This project is essentially a result of my attempt to under

Hamza Yusuff 6 Jun 1, 2022
Distributed lock manager. Warning: very hard to use it properly. Not because it's broken, but because distributed systems are hard. If in doubt, do not use this.

What Dlock is a distributed lock manager [1]. It is designed after flock utility but for multiple machines. When client disconnects, all his locks are

Sergey Shepelev 25 Dec 24, 2019
Tarmac is a unique framework designed for the next generation of distributed systems

Framework for building distributed services with Web Assembly

Benjamin Cane 192 Jun 26, 2022
Micro is a platform for cloud native development

Micro Overview Micro addresses the key requirements for building services in the cloud. It leverages the microservices architecture pattern and provid

Micro 11.2k Jun 27, 2022
A distributed systems library for Kubernetes deployments built on top of spindle and Cloud Spanner.

hedge A library built on top of spindle and Cloud Spanner that provides rudimentary distributed computing facilities to Kubernetes deployments. Featur

null 21 Jan 4, 2022
MIT 6.824: Distributed Systems

MIT 6.824 is a core 12-unit graduate subject with lectures, readings, programming labs, an optional project, a mid-term exam, and a final exam.

CC Chang 1 Jan 11, 2022
Distributed Systems 2021 - Miniproject 3

Distributed Systems 2021 -- Miniproject 3 Hand-in Date: 1 December 2021 (at 23:59) What to submit on learnit: a single zip-compressed file containing:

null 0 Dec 11, 2021
Labs, solutions and related materials from the MIT 6.824 Distributed Systems course.

MIT 6.824 Distributed Systems Labs, solutions and related materials from the MIT 6.824 Distributed Systems course. Overview From the official website:

Arindam Das 40 May 25, 2022
MIT6.824 Distributed Systems

MIT6.824-Distributed-Systems My Solutions for MIT6.824

null 0 Jan 28, 2022
Distributed reliable key-value store for the most critical data of a distributed system

etcd Note: The main branch may be in an unstable or even broken state during development. For stable versions, see releases. etcd is a distributed rel

etcd-io 40.4k Jun 30, 2022
Skynet is a framework for distributed services in Go.

##Introduction Skynet is a communication protocol for building massively distributed apps in Go. It is not constrained to Go, so it will lend itself n

null 2k Jun 12, 2022
a dynamic configuration framework used in distributed system

go-archaius This is a light weight configuration management framework which helps to manage configurations in distributed system The main objective of

null 195 Jun 17, 2022
A Distributed Content Licensing Framework (DCLF) using Hyperledger Fabric permissioned blockchain.

A Distributed Content Licensing Framework (DCLF) using Hyperledger Fabric permissioned blockchain.

Tal Derei 3 May 3, 2022
Flowgraph package for scalable asynchronous system development

flowgraph Getting Started go get -u github.com/vectaport/flowgraph go test Links Wiki Slides from Minneapolis Golang Meetup, May 22nd 2019 Overview F

Scott Johnston 49 Jun 18, 2022
distributed data sync with operational transformation/transforms

DOT The DOT project is a blend of operational transformation, CmRDT, persistent/immutable datastructures and reactive stream processing. This is an im

DOT & Chain 69 May 11, 2022
High performance, distributed and low latency publish-subscribe platform.

Emitter: Distributed Publish-Subscribe Platform Emitter is a distributed, scalable and fault-tolerant publish-subscribe platform built with MQTT proto

emitter 3.3k Jun 26, 2022
Fast, efficient, and scalable distributed map/reduce system, DAG execution, in memory or on disk, written in pure Go, runs standalone or distributedly.

Gleam Gleam is a high performance and efficient distributed execution system, and also simple, generic, flexible and easy to customize. Gleam is built

Chris Lu 3.1k Jun 22, 2022
Simplified distributed locking implementation using Redis

redislock Simplified distributed locking implementation using Redis. For more information, please see examples. Examples import ( "fmt" "time"

Black Square Media 721 Jun 20, 2022