Cloud BigtableService
BigTable: We have replaced our in-house key-value datamarketplace with BigTable.
LiveRamp on re-engineering around Google Cloud after migrating its big data environment from on-premise
2019-06-12·liveramp.fr ↗
Recommendations you can check.
Data connectivity and identity platform company.
5 things
Cloud BigtableService
BigTable: We have replaced our in-house key-value datamarketplace with BigTable.
LiveRamp on re-engineering around Google Cloud after migrating its big data environment from on-premise
2019-06-12·liveramp.fr ↗
Cloud SQLService
By moving lightweight databases into CloudSQL, application teams can completely own a MySQL instance without being DBAs; teams can think about the schema and not worry about backups or replication.
LiveRamp on re-engineering around Google Cloud after migrating its big data environment from on-premise
2019-06-12·liveramp.fr ↗
Google Kubernetes EngineService
By far the largest re-architecting we did while migrating to GCP was eliminating our on-premise Chef environment in favor of Kubernetes (via GKE), hosting images in GCR. While this was a large undertaking, it was 100% worth the time spent.
LiveRamp on re-engineering around Google Cloud after migrating its big data environment from on-premise
2019-06-12·liveramp.fr ↗
Google CloudService
While our migration plan erred on the side of directly translating our existing infrastructure onto GCP, there are many GCP tools we are using on day 1
LiveRamp on re-engineering around Google Cloud after migrating its big data environment from on-premise
2019-06-12·liveramp.fr ↗
BigQueryService
BigQuery: Although analytical queries are not a large percent of the computation we do at LiveRamp, they serve an important purpose — exposing our log data to Business Intelligence analysts without involving engineers.
LiveRamp on re-engineering around Google Cloud after migrating its big data environment from on-premise
2019-06-12·liveramp.fr ↗
Every entry is a verbatim quote and a link to the public post it came from. Nothing is paraphrased. If it is not on record somewhere public, it is not here.
The verdict is what they actually said: loved and liked are explicit; recommended means they told others to get it; uses means they only say they use it; read is a book on their public shelf with no verdict; mixed and disliked are kept too.
A dashed affiliate link, sponsored or their own label means the post disclosed a relationship. It is shown, never hidden.
The shading behind a date shows how dated a recommendation is for its kind of thing.
The shading behind a date shows how dated a recommendation is, for its kind of thing. Fully green is recent. It drains a quarter at a time as the post gets older, and is empty once it reads as dated.
What counts as old depends on the thing. A laptop praised four years ago has been replaced twice; a book loved twenty years ago is probably still loved. The shading is gone after about:
Stripes mean the post carries no date and the date shown is an estimate. No date at all, no shading.