Hacker News new | past | comments | ask | show | jobs | submit login

Hm, it feels like all of these except for number 2 and the last one can be solved by appropriate interfaces and documentation.



On that topic, I love this article from Stripe (in 2017) about how they version their APIs: https://stripe.com/blog/api-versioning


how about 1?

Imagine a scenario, your service is a low traffic, but service which embeds you as a library is a high traffic with many instances and always opens DB connection.

Why should you optimize your Database for high traffic use case, when your use case is really a low traffic?

And then repeat this for 10 other libraries and library owners. Everyone is optimizing for nothing.

make it even more difficult, 100 different types of services with different traffic patterns are embedding your library with different behaviours when it comes to managing DB connection state


how about 3?

Scenario: your service is accessing a service which exposes PII data and you only process them.

Service which embeds your service enabled audit logs of network requests and made it visible to everyone in the company. You have created a risk unintentionally




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: