It was not a big announcement from Google this week, but in a way it could be seen as a symbolic one.\nIn a blog post, Google announced new functionality that will allow its Cloud Endpoints API (Application Programming Interface) management platform to integrate with Amazon Web Service\u2019s Lambda functions-as-a-service product. The idea is you can build an application in Lambda and use Google Cloud\u2019s Endpoints to manage API calls associated with it.\n+MORE AT NETWORK WORLD: Serverless explainer: The next generation of cloud infrastructure +\nIt\u2019s a refreshing reminder that Google is willing and open to talking about customers using other vendor\u2019s cloud products and services, including from their biggest rival, AWS.\nGoogle certainly isn\u2019t cozying up to AWS. It\u2019s cloud chief Diane Greene this week put AWS in her crosshairs, predicting Google will top AWS within five years.\nWhen asked for comment, a Google spokesperson pointed out other ways that Google helps customers manage multiple clouds. It has a product named StackDriver that allows customers to monitor and log their use of not just Google\u2019s cloud but AWS too, for example.\nAWS has somewhat of a different story when it comes to hybrid and multi-clouds. For the first few years of the company\u2019s re:Invent conference, it spoke about how in the fullness of time most workloads would end up in the public cloud. In recent years, however, it has introduced tools that allow customers to connect their on-premises data centers or co-location facilities to the AWS public cloud. Products like Direct Connect, Amazon Virtual Private Cloud and the company\u2019s AWS Storage Gateway all are examples. It also recently announced a partnership with VMware that will allow workloads running in that software to run in AWS\u2019s cloud more easily.\nAt the recent AWS Summit in San Francisco CEO Andy Jassy said he believes hybrid clouds play an important role for customers\u00a0(he starts talking about it around the 8:30 minute mark in this video), but he says when push comes to shove, most enterprises and CIOs tend to choose to standardize on one cloud platform. There are multiple reasons for this, he says: Splitting workloads across clouds can force companies to standardize on the \u201clowest common denominator\u201d across cloud providers. Jassy argues that AWS is in a \u201cradically different\u201d stage of maturity in its products and services and is iterating more quickly than competitors. \u201cMost folks don\u2019t want to tie the hands of developers behind their backs in the name of splitting across clouds,\u201d Jassy says. Learning multiple platforms is a \u201cpain in the butt\u201d too, Jassy says. Trying to make the shift from on-premises to the cloud is hard enough, and learning multiple cloud platforms is an added, unnecessary layer of complexity, he says. Thirdly, he says customers diminish their buying power when spreading workloads across clouds because vendors offer volume-buying discounts, which are reduced if you don\u2019t run as many workloads in their clouds. If customers want to use multiple clouds for backup or redundancy, that can be done by using a multi-region approach all in AWS\u2019s cloud. \u201cWhen most CIOs and enterprises look at this carefully, they don\u2019t actually end up splitting (workloads) relatively evenly,\u201d Jassy said. \u201cThey predominantly pick one (vendor); others pick one and do a little bit with a second.\u201d\nThe perception is that Google is more open to multi-cloud workloads though, says Mike Kavis, an enterprise architect with consultant Cloud Technology Partners.\n\u201cGoogle\u2019s the most open to being multi-cloud, it\u2019s just in their DNA,\u201d he says. \u201cAlmost everything they do is open source.\u201d Most of the Amazon and Microsoft \u201chybrid\u201d tools, Kavis says, are basically on-ramps to get more data and workloads into their clouds. AWS would point out that their hybrid cloud tools allow for ingress into AWS\u2019s cloud to egress out of it, easing customers\u2019 lock-in concerns.\nTo an extent, this should not be surprising. Google has a heritage of being open source and given its market position of trailing AWS in market share \u2013 which Greene readily admits- it makes sense that Google would want to make it easy for customers to transfer workloads from AWS into Google. AWS, for its part, is growing healthily and has not yet seen a reason to build integrations with other public clouds. In the meantime, if customers really want to pursue a multi-cloud strategy, perhaps their best bet is relying on a third-party integration tool and not native tools from cloud providers.