Totally! I agree with everything you've said, their relatively lack of tech sophistication a huge PIA and it causes us daily headaches.
In addition, I've noticed that their hardware and software is often terrible, non-performant or buggy. So when we try to interface with them, we need to do hacks like severe rate limiting and long term caching of inventory (sometimes 24+ hours), simply because if we wanted to run at the TPS we run at, they would tip over. This leads to stale inventory on our end, and customer anger. We would love to do everything live (with short term caching), but the suppliers just can't take the load. Just about the only direct call made is the booking one, everything else is stale by some amount.
Monitoring/logging is often non-existent, so when you say "hey we're seeing latency" they have no idea how to diagnose or fix. Often, they don't have metrics in place and are unaware that there is latency to begin with.
> incomplete or inaccurate data produced by the property or hotel brand THEMSELVES
I believe it's largely because the RPC soap calls that many of these integrations use are stateful, so making the same call over and over again can lead to different results. Much of their tech stack is stuck in the 90s/early 2000s, and it shows.
In addition, I've noticed that their hardware and software is often terrible, non-performant or buggy. So when we try to interface with them, we need to do hacks like severe rate limiting and long term caching of inventory (sometimes 24+ hours), simply because if we wanted to run at the TPS we run at, they would tip over. This leads to stale inventory on our end, and customer anger. We would love to do everything live (with short term caching), but the suppliers just can't take the load. Just about the only direct call made is the booking one, everything else is stale by some amount.
Monitoring/logging is often non-existent, so when you say "hey we're seeing latency" they have no idea how to diagnose or fix. Often, they don't have metrics in place and are unaware that there is latency to begin with.
> incomplete or inaccurate data produced by the property or hotel brand THEMSELVES
I believe it's largely because the RPC soap calls that many of these integrations use are stateful, so making the same call over and over again can lead to different results. Much of their tech stack is stuck in the 90s/early 2000s, and it shows.