A common perspective that I see amongst software designers and developers is that Machine Learning and Artificial Intelligence (AI) are technologies which are only meant for an elite group. However, if a particular technology is to truly succeed and scale, it should be friendly with the common man (in this case a normal software developer).

Azure SQL Data Warehouse (DW) has quickly become one of the most important elements of the Azure Data Services landscape. Customers are flocking to Azure SQL DW to take advantage of its rich functionality, broad availability and ease-of-use. As a result, Talend’s world-class capabilities in data integration, data quality and preparation, and data governance are a natural fit with Azure SQL DW.

Since the release of Talend 7.1 users can build Talend jobs as Docker images and publish them to Docker registries. In this blog post, I am going to run through the steps to publish to the major cloud provider container registries (AWS, Azure and Google Cloud). Before I dig into publishing container images to registries, I am going to remind you the basics of building Talend Jobs in Docker images from Talend Studio as well as point out the difference between a local build and a remote build.

In Yellowfin 8 we introduced two new products, Yellowfin Signals, to automatically discover the most critical changes in your business as they happen, and Yellowfin Stories, to provide context to the numbers and tell compelling stories with your data. We’ve received great feedback since then and implemented some of the requested enhancements to improve the user experience, increase governance and performance.

In my last post, I gave you the first six Do’s and Don’ts of Data Governance and promised to bring together an additional six to consider when making a data governance plan for your organization. Here are six more dos and don'ts when building your data governance framework.