Systems | Development | Analytics | API | Testing

While humans are ever-adapting, the recent pandemic has forced a complete revamp of how we work and play. As in-person meetings and conventions remain sparse, networking in other ways has become a new normal. Mobile app developers are applying key lessons and trends of online networking and socializing to capitalize on increasing global demand for virtual connectivity.

Several years ago when I was working on a big data project, I saw something a data engineer shouldn’t see. Curious to understand the level of detail in a new credit score dataset we’d received in our data lake, I queried it. I was surprised at how easily and suddenly my screen was flooded with the mortgage history, overdraft limits and year-end financial statements of my colleagues, and I felt deeply uneasy.

Although the issue of silos in IT and data management are well known, companies appear to be falling back into this trap by not distributing their artificial intelligence (AI) and machine learning (ML) capabilities across their business. New research from Qlik and IDC revealed that just 20 percent of businesses widely distribute these capabilities across the organization.

Migrating a data warehouse from a legacy environment requires a massive upfront investment in resources and time. There is a lot to consider before and during migration. You may need to replan your data model, use a separate platform for tasks scheduling, and handle changes in the application’s database driver. Therefore, organizations must take a strategic approach to streamline the process. This article presents a step-by-step approach for migrating a data warehouse to the cloud.

It’s no exaggeration to say that today’s internet is built on JavaScript. Around 95% of all websites have been built using the language, according to the latest figures. JavaScript has evolved beyond the client side and is now used to construct entire technology stacks, not to mention support databases like pouchdb and RethinkDB.

The device landscape is as vast as it is complex. With at least 63,000 possible device profiles reported—a number growing at almost 20% per year—the scale of device fragmentation is staggering. New models, operating systems, browsers, screen resolutions, etc., make it extremely difficult for web and app developers to deliver a consistently flawless user experience across all combinations.