Launch HN: GoLinks (YC W19) – Internal short links for teams

Re:Launch HN: GoLinks (YC W19) – Internal short links for teams by jedberg on Friday March 08, 2019 @11:30PM (#19344463)

I think this is super useful and you're totally right about how go spreads. At Netflix we ended up rewriting go at least three times. Every time someone new took it over, they rewrote it. Having a go service with no work is super useful.

I set it up but didn't look carefully -- is there an export function? And an API? I think I could get around most of my concerns if I could just get a CSV each day of all the current links, just in case something happens to you guys.

Another source of comfort would be if you could give me a lambda function that I could deploy into my own AWS that would just resolve go links. So all the management would happen on your platform, but the actual resolution would be on my side so I would be in control of its reliability. I know that at Netflix we built go to be highly reliable because in an outage, go was actually essential infrastructure to get us to the tools and dashboards we need most.

Thanks for making this!

[ Parent | on HN ]

Re:Launch HN: GoLinks (YC W19) – Internal short links for teams by seantomburke on Saturday March 09, 2019 @01:47AM (#19344860)

We do plan on creating an API that will allow users to create links, and view links through integrations, but it isn’t built currently. That’s an interesting solution for resolution, but I can definitely see the utility in having the resolution be in a lamda function, to ensure reliability. We don’t have a daily export function, but can provide links to companies in the rare event that something happens to us.

[ Parent | on HN ]