> What industries is it common ... perform better than the ones built with coordination with the storage engine and everything else ...
Uber for one as documented here https://www.uber.com/us/en/blog/schemaless-part-one-mysql-da...
There are many more and most may not be documented online.
Our usecase is offline first mobile ERP (roll-out hopefully soon) with online-sync capabilities doing invoice/coupon processing, etc. in a network of regional shops - with a focus on minimizing latency and aggressive reduction of costs at scale.
Once we measured the reduction in latency due to parallel fanout (over index shards - not just data shards) for range scan, there is no going back ever again.
When you need the same database to be running on mobiles and servers alike, you need embedded database for mobile and standalone executable for server.
> they will perform better than the ones built with coordination with the storage engine and everything else?
No amount of coordination with the storage engine can override the physics of lock contention in distributed systems.
> This seems a very unusual set of circumstances so I'm very curious on the use case.
Not with my background. Its the norm :)
Uber for one as documented here https://www.uber.com/us/en/blog/schemaless-part-one-mysql-da...
There are many more and most may not be documented online.
Our usecase is offline first mobile ERP (roll-out hopefully soon) with online-sync capabilities doing invoice/coupon processing, etc. in a network of regional shops - with a focus on minimizing latency and aggressive reduction of costs at scale.
Once we measured the reduction in latency due to parallel fanout (over index shards - not just data shards) for range scan, there is no going back ever again.
When you need the same database to be running on mobiles and servers alike, you need embedded database for mobile and standalone executable for server.
> they will perform better than the ones built with coordination with the storage engine and everything else?
No amount of coordination with the storage engine can override the physics of lock contention in distributed systems.
> This seems a very unusual set of circumstances so I'm very curious on the use case.
Not with my background. Its the norm :)