Skip to content

eddyzags/resolver

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

21 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Resolver

Resolver is a grpc resolver using Marathon framework for service discovery. A minimalistic library that uses Marathon, which is a container orchestration platform for Apache Mesos and Datacenter Operating (DC/OS), to interact with other services using name-based system discovery. Plus when scaling a service, the resolver is able to monitor all the running service's tasks simultaneously.

Features

  • Round-robin load balancing with gRPC
  • Service name discovery (collision supported)
  • High availability with Marathon

Dependencies

  • Marathon: A production-grade container orchestration platform for Mesosphere's Datacenter.
  • gRPC-Go: Go implementation of gRPC. A high performance, open source, general RPC framework.

Installation

Install the resolver using the "go get" command:

go get github.com/eddyzags/resolver

Import the library into a project:

import "github.com/eddyzags/resolver"

Usage

Resolver uses Marathon labels feature in order to identify resident services in the cluster. The label is composed of the service unique name and the port index. Those two informations will allow the resolver to identify the tasks ip addresses and the port on which the grpc client should establish a connection.
Let's start with a simple app definition:

{
  "id": "my-app",
  "cpus": 0.1,
  "mem": 64,
  "container": {
    "type": "DOCKER",
    "docker": {
      "image": "eddyzags/healthy:latest",
      "network": "BRIDGE"
    },
    "portMappings": [
      {
        "containerPort": 80,
        "hostPort": 0
      },
      {
        "containerPort": 4242,
        "hostPort": 0
      }
    ]
  },
  "labels": {
    "RESOLVER_0_NAME": "my-app-service"
  }
}

We have just defined an application called my-app with a service resolver name of my-app-service which points to the port index 0.

A service resolver name can be defined using a labels map:

"RESOLVER_{PORTINDEX}_NAME": "{NAME}"

Once we deployed the application in Marathon, the service can be discovered through its name in the grpc client instantiation.

package main

import (
       "log"

       "github.com/eddyzags/resolver"

       "google.golang.org/grpc"
       pb "google.golang.org/grpc/examples/helloworld/helloworld"
)

func main() {
     resolver, err := resolver.New("marathon.mesos:8080")
     if err != nil {
        log.Fatalf("couldn't instantiate resolver: %v", err)
     }

     b := grpc.RoundRobin(resolver)

     conn, err := grpc.Dial("my-app-discovery", grpc.WithBalancer(b))
     if err != nil {
        log.Fatalf("couldn't dial grpc server: %v", err)
     }
     defer conn.Close()

     c := pb.NewGreeterClient(conn)

     r, err := c.SayHello(context.Background(), &pb.HelloRequest{Name: "user1"})
     if err != nil {
         log.Fatalf("couldn't send say hello request: %v", err)
     }

     log.Printf("Response: %s\n", r.Message)
}

Releases

No releases published

Packages

No packages published

Languages