After what struck me as a comparatively dry spell of product bulletins in 2021, AWS spent re:Invent 2022 launching a bunch of latest providers. AWS Chief Evangelist Jeff Barr, with assist from some AWS developer advocates, summarized probably the most impactful bulletins as a result of “there’s merely an excessive amount of nice stuff for the workforce to cowl,” however then they proceeded to spend greater than 2,700 phrases highlighting their favourite bulletins, which appeared to incorporate… all the things. Mainly, they handed out participation trophies to each AWS service workforce. Not notably useful.
They might have highlighted automated knowledge preparation for Amazon QuickSight Q, given how tough knowledge preparation will be for machine studying. Or what about Amazon Safety Lake, which routinely centralizes an organization’s safety knowledge from cloud and on-premises sources into an information lake. Very cool. What about Amazon CodeCatalyst, which RedMonk analyst James Governor rightly characterizes as “a packaging train” designed to enhance software program growth and supply and result in larger comfort (“the killer app”). Additionally, very cool.
If we glance past the gazillion new providers and updates to current providers that AWS introduced, an rising theme portends a dramatically completely different (and higher) AWS. Sure, I’m speaking about integration as a necessary product characteristic.
Much less meeting required
AWS used to tout its 200+ providers. Not anymore. In reality, there are in all probability nearer to 400 AWS providers now, however in some unspecified time in the future prior to now two years, AWS realized that having so many providers sophisticated clients’ IT selections quite than simplifying them.
For these unfamiliar with how AWS operates, every service (product) workforce runs autonomously. There may be some top-down course, however as a common rule, particular person service groups construct what they really feel clients most need, even when that results in inter-team competitors. That is each a characteristic (autonomous groups can construct sooner) and a bug (autonomous groups don’t essentially coordinate to make it simple to make use of a number of AWS providers harmoniously). Clients are sometimes left to cobble collectively disparate providers with out tight integration in the way in which Microsoft would possibly present, for instance.
All this makes the introduction of Amazon Aurora zero-ETL integration with Amazon Redshift such a jaw-dropper.
Let’s be clear: In essence, AWS introduced that two of its providers now work effectively collectively. It’s greater than that, after all. Eradicating the fee and complexity of ETL is an effective way to take away the necessity to construct knowledge pipelines. At coronary heart, that is about making two AWS providers work exceptionally effectively collectively. For an additional firm, this is likely to be thought-about desk stakes, however for AWS, it’s comparatively new and extremely welcome.
It’s additionally an indication of the place AWS could also be headed: tighter integration between its personal providers in order that clients needn’t tackle the undifferentiated heavy lifting of AWS service integration.
Making room for third events
That zero ETL announcement, as potent because it was, would have been even higher had AWS additionally highlighted seamless integrations with third-party providers similar to Databricks or DataStax. AWS might not like to make use of the “P” phrase (“platform”), however that doesn’t change actuality. AWS is the world’s largest cloud platform, and AWS clients rightly count on to have the ability to combine their most popular software program with AWS.
That is what makes Amazon DataZone so fascinating.
Amazon DataZone is a “knowledge administration service that helps you catalog, uncover, analyze, share, and govern knowledge throughout the group,” writes Swami Sivasubramanian, AWS vice chairman of information and machine studying. This could be cool if all it did was pull collectively all the info saved in repositories from numerous AWS providers, which it does with integrations to AWS providers like Redshift, Athena, QuickSight, and extra. DataZone goes past this by providing APIs to combine with third-party knowledge sources from companions or others.
On the one hand, it’s apparent that AWS would have to present such APIs, as a result of after all, not all (and even most) buyer knowledge sits in AWS. Within the FAQ accompanying the announcement, AWS even talked about that DataZone can observe knowledge in rival cloud suppliers like Google Cloud and Microsoft Azure—multicloud, anybody? However it’s additionally not apparent. In spite of everything, the tech trade has spent many years watching Apple, Microsoft, and others ignore aggressive merchandise exterior their very own walled gardens. By emphasizing the necessity to entry non-AWS knowledge sources, DataZone might be a number one indicator of AWS going past grudging acceptance of third-party knowledge sources or providers to emphatic embrace.
Opening up
Then there was the announcement that wasn’t an announcement in any respect. AWS introduced Trusted Language Extensions for PostgreSQL on Amazon Aurora and Amazon RDS. PG.TLE is an open supply growth equipment for constructing PostgreSQL extensions. It “supplies database directors management over who can set up extensions and a permissions mannequin for working them, letting software builders ship new performance as quickly as they decide an extension meets their wants.”
Good, proper?
What wasn’t introduced and by no means will probably be is the truth that AWS is arguably the second-largest employer of PostgreSQL contributors, simply behind CrunchyData. I’ve instructed earlier than that AWS has more and more seen the necessity to contribute to the open supply initiatives upon which its managed providers (and its clients) rely. AWS worker contributions to PostgreSQL are a robust instance of this.
All of this implies that AWS is changing into much less insular daily. The corporate has at all times seen “buyer obsession” as its most vital success metric, and generally service groups felt the fitting strategy to obtain that was to construct the very best service in isolation from the shopper’s current IT investments, together with different AWS providers. It additionally led some groups to restrict their involvement in upstream open supply initiatives and attempt to ship a self-contained model of that challenge in order to higher management the shopper expertise.
As these and different re:Invent bulletins recommend, AWS more and more builds neighborhood—whether or not companions, open supply initiatives, and even different aggressive merchandise—into its providers. That’s nice for patrons and nice for AWS.
Copyright © 2022 IDG Communications, Inc.
