Create and deliver personalized experiences across digital properties at scale
Build engaging websites with intuitive web content management
Leverage a complete UI toolbox for web, mobile and desktop development
Build, protect and deploy apps across any platform and mobile device
Build mobile apps for iOS, Android and Windows Phone
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
Automate UI, load and performance testing for web, desktop and mobile
Host, deploy and scale Node.js, Java and .NET Core apps on premise or in the cloud
Optimize data integration with high-performance connectivity
Automate decision processes with a no-code business rules engine
Transform your businesses in order to survive in a completely digitized and connected world driven by software innovation.
Globally scale websites with innovative content management and infrastructure approaches
Content-focused web and mobile solution for empowering marketers
Faster, tailored mobile experiences for any device and data source
UX and app modernization to powerfully navigate today's digital landscape
Fuel agility with ever-ready applications, built in the cloud
ADO.NET vNext has rightly absorbed much of my attention of late, and rightly so as this is an major focus on the .NET Framework roadmap. No matter how much is made of the perceivedcompetition between Redmond and Mountain View, I am sure the latest announcements from Google have not gone unnoticed.
This caught my eye today while browsing the ZDNet blog portal. As a potentially significant development, and given the topics I talk about on this blog, it goes without saying that I will certainly be playing with this. Some key highlights include the availability of a ReSTful interface, a full set of CRUD functionality and as you might expect a bulk load mechanism.
I was immediately struck that accessing structured data such as produced by Google Base seems like an ideal task for XQuery, particularly DataDirect XQuery. Google's ReSTFul interface produces Atom (RSS) feed which are easily processed by many tools. However, this is just half the story and I don't believe exposing this information in a well thought out API is enough. Far more compelling might be to join this with data you have on your internal data sources, such as relational databases or other XML feeds and then you have a compelling integration story - do this efficiently, then you really have a compelling solution.
The is no doubt that the usefulness of this scenario is also highly dependent on the information available in Google Base. Criticality, Google allows anyone to store, or indeed post their information on Google Base. Mapping the more semantic data groupings might be a challenge for some applications, but with customizable item types, the possibilities seem limitless.
Mashups are already a trendy Web 2.0 word for bringing together information, people and communities. Automating, optimizing and managing collaborative information, such as can be stored in Google Base, together with the right XQuery implementation may well drive the next wave data integration.
View all posts from Jonathan Bruce on the Progress blog. Connect with us about all things application development and deployment, data integration and digital business.
Copyright © 2016, Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks or appropriate markings.