Re:Launch HN: GoLinks (YC W19) – Internal short links for teams
by badfrog on Friday March 08, 2019 @04:05PM
(#19342170)
My understanding of the first concern was that users are in trouble if GoLinks shuts down or has an outage. Do you have any mitigation plan for such cases?
Re:Launch HN: GoLinks (YC W19) – Internal short links for teams
by seantomburke on Friday March 08, 2019 @05:36PM
(#19342893)
Yep, It’s in our terms of service, in the unlikely case something happens to GoLinks, we will provide you with all your links. But we plan on being around for a long time.
Re:Launch HN: GoLinks (YC W19) – Internal short links for teams
by 3into10power5 on Friday March 08, 2019 @07:03PM
(#19343451)
Grandparent asked about outage. Not about going out of business.
Re:Launch HN: GoLinks (YC W19) – Internal short links for teams
by seantomburke on Friday March 08, 2019 @07:35PM
(#19343622)
Outages are definitely a risk every company encounters. Whether it's a third-party hosted solution or an internal solution, unfortunately, servers do go down. We run all our services on AWS which provides an uptime SLA of at least 99.99%, so uptime shouldn't be a problem, but we do recognize the concern.
Re:Launch HN: GoLinks (YC W19) – Internal short links for teams
by h1d on Saturday March 09, 2019 @12:45AM
(#19344701)
Services can also go down when the infrastructure is up too.
Self hosted solution can give that responsibility away though.
Re:Launch HN: GoLinks (YC W19) – Internal short links for teams
by davidjnelson on Saturday March 09, 2019 @01:27PM
(#19347602)
Your product is a really smart idea. I wonder if adding an on premise solution would help sales with larger orgs. Sort of like what GitHub did with GitHub Enterprise.
The second, our links are actually more human-parsable. go/customer-feedback is much more readable than https://docs.google.com/d/document/ABCDE1234/. You actually wouldn't know if the google doc is relevant without opening it. This might be surprising, but many companies with a similar system actually don't maintain them very well. It works the first time when a tools team builds it, but when those engineers leave the company, new engineers will either try to revive the old system, or rewrite the entire system from scratch to maintain it. We continue to improve the product over time with customer feedback and can provide analytics for the most common links used in the company.
There currently isn't a solution specifically solving these issue on the market today.
Hope this helps!