3 ms·
When you use a library from an outside source, if you update that library, it might break your build. When you use an outside service, they might break your sy
by taneq 3y ago
When you use a library from an outside source, if you update that library, it might break your build.
When you use an outside service, they might break your system at a time of their choosing.
- mooreds 3y agoExactly. It'll break sometime (it's software). So when do you want it to break? And is the benefit of controlling/planning the timing of that breakage worth the cost of operating the software? As always, it depends. Questions I'd ask: * How critical is the software to your application's proper functioning? * How big is the team? * Who are your customers and what are customer expectations around your application's proper functioning? * How often does the library change? * What expectations does a service set around backwards compatibility? What commitments are made?
- nijave 3y ago>When you use an outside service, they might break your system at a time of their choosing. Well sure, but if this is important to you, you might consider a contract with the company that lays out cases and conditions where breakage is acceptable.
- marcosdumay 3y agoOr you internalize the functionality with a library.
- TeMPOraL 3y agoYes, SLA is a way to turn literal existence of a product into a pay-as-you-go offer on top of a service.
- JohnFen 3y agoYes. And if an updated library breaks you, you can fix it easily by rolling back to the earlier version of the library. If an outside service breaks you, you're hosed until they fix the service or you rework your code to route around the breakage.