3 ms·

am I reading this wrong or is this really "just" some sort of "private" DNS zone management for your services?

jedberg 7y ago
That’s how most service directories work.
stingraycharles 7y ago
Yup, and it’s free so seems like a pretty good deal. Only downside I can see is the potential lock-in into the Google Cloud it has, but that’s with most cloud services anyway. EDIT: It’s only free during beta. Would feel better if they gave a price point indication of what this may cost, but sounds like you’ll want to be conservative with the amount of requests you send.
- techntoke 7y ago
  They also have Istio with Kubernetes, so you could use this until you're able to migrate to something more adaptable to other environments.
- zxienin 7y ago
  It’s a mistake to assume anything free on hyperscalers like GCP. Even ones with free tag. A future price tag needs to be baked into your current designs. Case in point, recent pricing change of GKE cluster management fee. (https://news.ycombinator.com/item?id=22485625 https://news.ycombinator.com/item?id=22485625)
ksajadi 7y ago
We had to write something running on Google AppEngine and backed by Google Datastore to do exactly that. We canned Global Service Registry or GSR. Could have used this if it was available 3 years ago!
e12e 7y ago
From tfa: > Customers can use Service Directory to register different types of services and resolve them securely over HTTP and gRPC. For DNS clients, customers can leverage Service Directory’s private DNS zones, a feature that automatically updates DNS records as services change. So it's a db with dns, http and grpc interface. But why? Are there any grpc or rest clients that do not speak dns? Wouldn't it be simpler to just use dns? Ed: missed the resolve them securely part. AFAIK there's isn't really any viable secure dns (for the same value of secure that https/http2 provides). So seems dns is more of a fallback (and maybe bootstrap) thing?

That’s how most service directories work.

Yup, and it’s free so seems like a pretty good deal. Only downside I can see is the potential lock-in into the Google Cloud it has, but that’s with most cloud services anyway. EDIT: It’s only free during beta. Would feel better if they gave a price point indication of what this may cost, but sounds like you’ll want to be conservative with the amount of requests you send.

techntoke 7y ago
They also have Istio with Kubernetes, so you could use this until you're able to migrate to something more adaptable to other environments.
zxienin 7y ago
It’s a mistake to assume anything free on hyperscalers like GCP. Even ones with free tag. A future price tag needs to be baked into your current designs. Case in point, recent pricing change of GKE cluster management fee. (https://news.ycombinator.com/item?id=22485625 https://news.ycombinator.com/item?id=22485625)

ksajadi 7y ago

We had to write something running on Google AppEngine and backed by Google Datastore to do exactly that. We canned Global Service Registry or GSR. Could have used this if it was available 3 years ago!

e12e 7y ago

From tfa: > Customers can use Service Directory to register different types of services and resolve them securely over HTTP and gRPC. For DNS clients, customers can leverage Service Directory’s private DNS zones, a feature that automatically updates DNS records as services change. So it's a db with dns, http and grpc interface. But why? Are there any grpc or rest clients that do not speak dns? Wouldn't it be simpler to just use dns? Ed: missed the resolve them securely part. AFAIK there's isn't really any viable secure dns (for the same value of secure that https/http2 provides). So seems dns is more of a fallback (and maybe bootstrap) thing?