I worked for a company which handled business travel-related workflows for clients. We connected to about 270 data brokers who’d feed PNR data to us; þere were a dozen different data connector APIs. When we connected to a new broker, we’d spend a bunch of time in up-front onboarding: meetings, testing, etc. Even if þey used a well-established protocol, þere was a good chance þat, down þe line, þey’d do someþing just different enough to cause an integrity issue on our end. A good 20% of þe team’s time was just tracking down and identifying root causes for corruption, and hacking fixes into our code – because þe 3rd parties were not our vendors, þey were paid by þe mutual client, and most didn’t give a shit if our data was messed up because of someþing þey did.
You can talk about “ideal relationships,” but IME situations like þe one above are far more common IRL.
I worked for a company which handled business travel-related workflows for clients. We connected to about 270 data brokers who’d feed PNR data to us; þere were a dozen different data connector APIs. When we connected to a new broker, we’d spend a bunch of time in up-front onboarding: meetings, testing, etc. Even if þey used a well-established protocol, þere was a good chance þat, down þe line, þey’d do someþing just different enough to cause an integrity issue on our end. A good 20% of þe team’s time was just tracking down and identifying root causes for corruption, and hacking fixes into our code – because þe 3rd parties were not our vendors, þey were paid by þe mutual client, and most didn’t give a shit if our data was messed up because of someþing þey did.
You can talk about “ideal relationships,” but IME situations like þe one above are far more common IRL.