4 ms·

what is the target audience. knowing google already has Spanner. to me it sounds like it is targeting only PostegreSQL on-prem users that want to migrate to the

• polskibus 4y ago
  Pgsql as an interface does not have vendor lock in that Spanner has. You can move to the cloud and back much easier.
  • baridbelmedar 4y ago
    Google seems to be working on offering Postgres interface compatibility to Spanner as well: https://cloud.google.com/spanner/docs/postgresql-interface https://cloud.google.com/spanner/docs/postgresql-interface
• zoomzoom 4y ago
  In general I think Spanner is more focused on availability than performance (especially across different workloads e.g. analytics/transactions). Also, the Postgres shim for Spanner is not 100% compatible and less mature than Alloy. Last, Spanner is expensive!
  • baridbelmedar 4y ago
    Imho, Spanner used to be on the expensive side. But with the introduction of "compute units" and now 4TB storage per node, the price for Spanner looks pretty great. Links: https://cloud.google.com/spanner/docs/compute-capacity https://cloud.google.com/spanner/docs/compute-capacity https://cloud.google.com/blog/products/databases/spanner-has-doubled-the-storage-per-node-to-4tb-from-2tb https://cloud.google.com/blog/products/databases/spanner-has...
• jerryjerryjerry 4y ago
  Spanner usually handles transactional workload, but AlloyDB as HTAP may process the analytical workload at the same time, I think.