3 ms·
My problem with this is how it's priced. Why am I paying for instance hours when I don't have/need instance access. I would have thought it'd be priced like Dat
by oxplot 9y ago
My problem with this is how it's priced. Why am I paying for instance hours when I don't have/need instance access. I would have thought it'd be priced like Datastore per GB used and API calls made. As it sits right now, it's fairly expensive.
- bbass 9y agoAs a heavy user of datastore, i'm glad the pricing model is around instances and data stored. Paying for reads and writes makes doing any sort of migrations or map reduce jobs extremely expensive.
- all_blue_chucks 9y agoThe bottleneck likely isn't I/O. My guess is it's RAM. RAM ain't cheap.
- manigandham 9y agoThey aren't actual VM instances, just blocks of compute and storage. BigTable is priced the same way. At the scale they're targeting, it makes sense, especially for large companies who will gladly pay for the reduced complexity and easy scaling while removing all the operational overhead and cost of other solutions that don't come close to this.