3 ms·
There's also the point about vendor lock-in, in AWS you do need a systems engineer to setup and automate infrastructure, but pretty much everything (aside from
by piva00 12y ago
There's also the point about vendor lock-in, in AWS you do need a systems engineer to setup and automate infrastructure, but pretty much everything (aside from a few products like Redshift, Dynamo and EMR is what I recall from my mind) you can port out of AWS pretty easily if and when the time comes to have your own data center and cut some costs.
Google Cloud is a much bigger vendor lock-in, you could not setup the same environment outside of it.
- vgt 12y agoI'm genuinely curious why you hold that opinion, especially in context of a thread that discusses a service that's available through the standard hbase api
- rodionos 12y agoWithout support for co-processors in BigTable I would hardly call it 'standard' API. Also the implementation of buffered mutation, a key attraction in HBase 1+ for fast non-blocking writes, is different enough in bigtable that you might have to change application code to work it consistently. It's nice though that bigtable API have references to HBase bugs :) > HBase 1.0.0 has a bug in it. It returns maxSize instead of the buffer size for > getWriteBufferSize. https://issues.apache.org/jira/browse/HBASE-13113 https://issues.apache.org/jira/browse/HBASE-13113
- megaman821 12y agoI think of the three AWS services you named, only Dynamo can't easily be ported out. Redshift use Postgres drivers. EMR uses the HBase API.
- eropple 12y agoRedshift uses Postgres drivers, but does not use Postgres semantics. Important to consider if you're using any nontrivial amount of data, because porting it even to other cstore databases will require a lot of thinking and probably some munging-at-scale.
- 23david 12y agoEver try porting a customer using cloudformation templates and autoscaling groups over to another cloud service? Or reimplementing s3 or EBS semantics? It can be done, but definitely non-trivial... lockin++