The Latest

22 October 2021: At Google Cloud Next ’21, Google announced the general availability of a PostgreSQL interface to its hyperscale, global spanning Spanner relational database. In short, this means that organisations that have applications that are compatible with PostgreSQL can now migrate to a highly elastic database that is significantly less costly, more robust than running PostgreSQL instances on virtual machines.


Why it’s Important.

Google’s highly scalable Cloud relational Spanner database provides high-velocity transactions, strong consistency, and horizontal partitioning across global deployments. Like other specialised, serverless Cloud databases, Spanner previously required legacy (on-premises) applications’ data access layers to be reworked. 

The addition of a PostgreSQL interface greatly reduces development teams’ workload for migrating applications to Spanner. This has several knock-on impacts when migrating applications to the Cloud, including: 

  • reducing training  / new skills development, and allowing existing skills to be fully leveraged
  • reducing the vector for new bugs to be introduced
  • simplifies testing

Overall, this significantly lowers the cost and risk of moving an app to the Cloud. 

As always, the devil is in the detail. Cloud Spanner Product Manager, Justin Makeig posted that the platform does not yet have universal compatibility for all PostgreSQL features, since the company’s goal was to focus on portability and familiarity. However, IBRS has determined that even with the current level of functionality, the PostgreSQL interface for Spanner presents good value for teams looking to migrate legacy applications to the Cloud.

Google is not the only hyperscale Cloud vendor that has enabled this type of operability. However, Cloud Spanner is more economical than competitive hyperscale Cloud database products at this time.


Who’s impacted

  • Development team leads
  • Cloud architecture teams


What’s Next?

Google announced that it is planning to expand its Spanner integration to additional database standards. Data portability and migration of legacy applications to hyperscale Cloud is now a focus for many ICT groups. The availability of open standard SQL interfaces to database PaaS (platform-as-a-Service)  is expected to be a trend for application and data migration, especially where the applications are complex.


Related IBRS Advisory

  1. VENDORiQ: Google introduces Database Migration Service

  2. Enterprise resource planning (ERP) Part 5: Will automation of S/4HANA data migration make modernisation

The Latest

16 February 2021: Veeam continues to expand its footprint across the hyperscale Cloud vendors with the introduction of Veeam Backup for Google Cloud Platform. This follows its December 2020 announcement when Veeam announced the general availability of AWS v3 Backup and Azure v4 Backup. As a result, Veeam now provides backup and recover capabilities across - and just as importantly between - the three major hyperscale Cloud vendors. 

Why it’s Important

During a briefing with IBRS, Veeam detailed its strong growth in the Asia Pacific region. It also discussed its strategy for providing backup and recovery capabilities over the major hyperscale Cloud services: Azure, AWS and Google. The demand for Cloud backup and recovery is growing with greater recognition organisations adopting hybrid Cloud (the most likely future state for many organisations) demands more consistent and consolidated approaches to management - including backup and migration of data between Clouds. VMWare is seeing growth in its hybrid Cloud management capabilities as well, and the synergy between Veeam and VMWare productions is no coincidence.  

Who’s Impacted

  • Cloud architects
  • Business continuity teams

What’s Next?

Backing up Cloud resources appears to be a simple process. Taken on as service-by-service, this might be true. However, in reality the backup becomes increasingly challenging. As more and more applications are made up of a myriad of components, this leads to a rapidly evolving ecosystem of solutions. Hence, data recovery and restoration are also getting more complex. This is further exacerbated by the growing adoption of hybrid Cloud. 

Organisations need to explore backup and recovery based on not only current state Cloud architecture, but possible migration between Cloud services and where different integrated applications reside on different Cloud platforms.

Related IBRS Advisory