[Devops] Microsoft Server Deployment Plan

[Selcuk Bozdag]

Hi,

Our requirements state that we should run our services on a Microsoft Server 2012 VM.
We have 9-10 gRPC services running on different ports.

One option is to let our desktop clients know about services and their connection parameters (ip and port information) for each.
Other one is to have a proxy server and our clients communicate services through the proxy. But we could not figure out that.

There may be some other points we have not thought about. Coming from a monolith world, we are a bit new to the microservices in terms of devops.

What is your recommendation deployment plan for this scenerio?  What tools do you recommend?

Thanks so much

[Spencer Fang]

Hi Selcuk,

Either way, you probably do not want to hard code machine IP:PORT info into clients. In grpc we typically want to connect to a name, and let the NameResolver turn that name into a set of HOST:PORTs for us. That way you have the ability to have redundancy and let grpc do load balancing. Whether your applications shall talk directly to these micro services, or go through some sort of gateway service depends on your needs, but I'd err on the side of hiding architectural details from clients.

Are your clients connecting across the public internet? 

--
You received this message because you are subscribed to the Google Groups "grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+unsubscribe@googlegroups.com.
To post to this group, send email to grp...@googlegroups.com.
Visit this group at https://groups.google.com/group/grpc-io.
To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/cf78d95d-2408-47a8-b762-049e4e089094%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Spencer Fang

[Selcuk Bozdag]

Hi,

No, our clients aren't connecting across the public internet.

So, as far as I get, we need a name resolver.
What else do we need for a successful deployment?
Thanks

[Spencer Fang]

The only included NameResolver is a DnsNameResolver, which is the class that the grpc client uses to turn something like "myserver.example.com" into a set of hosts. Other people in the community have opted to use things like Zookeeper and etcd instead of DNS, and wrote their own custom NameResolvers. Are you in an environment where your servers can be set up with a DNS name?

--
You received this message because you are subscribed to the Google Groups "grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+unsubscribe@googlegroups.com.
To post to this group, send email to grp...@googlegroups.com.
Visit this group at https://groups.google.com/group/grpc-io.

To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/8b844350-92a7-4c41-82d5-1fa0ba5bb4d6%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Spencer Fang

[Selcuk Bozdag]

Hi,

Sorry for the late response. All our services will be deployed on a single machine. And the server will have a DNS name. Thanks.

On Saturday, 15 July 2017 01:40:27 UTC+3, Spencer Fang wrote:

The only included NameResolver is a DnsNameResolver, which is the class that the grpc client uses to turn something like "myserver.example.com" into a set of hosts. Other people in the community have opted to use things like Zookeeper and etcd instead of DNS, and wrote their own custom NameResolvers. Are you in an environment where your servers can be set up with a DNS name?

On Fri, Jul 14, 2017 at 2:50 PM, Selcuk Bozdag <selcuk...@gmail.com> wrote:

Hi,

No, our clients aren't connecting across the public internet.

So, as far as I get, we need a name resolver.
What else do we need for a successful deployment?
Thanks

--
You received this message because you are subscribed to the Google Groups "grpc.io" group.

To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+u...@googlegroups.com.

To post to this group, send email to grp...@googlegroups.com.
Visit this group at https://groups.google.com/group/grpc-io.

To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/8b844350-92a7-4c41-82d5-1fa0ba5bb4d6%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Spencer Fang

[spenc...@google.com]

Hi Selcuk, since the architecture is quite simple, I don't see any problems with just having clients connect to the "hostname:port" of the single machine right now.