3 ms·

> When Google announced in 2018 that it was shutting down goo.gl, the company encouraged developers to migrate to Firebase Dynamic Links (FDL) — which has also

• fodkodrasz 2y ago
  THIS! Seriously... if they retire it, make the backend read-only, that way it can be highly optimized, and ran with minimal costs (from a mammoth company's perspective). I don't know, make it an interview question and deploy the best answer? They put more effort into tortuting aspirants than to EOL-ing some of their cheap-ass services in a reasonable way.
  • ajb 2y ago
    In S3, you can implement this with a single bucket, no code at all: objects can cause redirects, using x-amz-website-redirect-location Since Google buckets don't seem to implement this feature, maybe they should point goo.gl at S3 :-)
    • sofixa 2y ago
      Oh cool, I've done this sort of thing (mass redirects) with Lambda@Edge which allows for more flexibility, but probably costs more.
  • bdd8f1df777b 2y ago
    The problem is that Google infra requires everything running to be new. There is a build horizon of 6 months. Everything built with code older than 6 months is not able to run on Borg. And since Google deprecates many internal infra tools/libraries routinely, a team is required to make sure the service remains up-to-date. Google doesn't want to pay for such maintenance.
    • karmakaze 2y ago
      This what I'd suspected as pressure to discontinue services that could otherwise virtually maintenance-free at low cost.