I have been having quite a bit of fun in this blog series exploring the “sliding doors” (or divergent paths) that organizations can take with their AI and data initiatives. The right door can lead to great value, as I covered in my previous posts on ESG reporting, data products, and responsible AI.

HubSpot, Snowflake and Fivetran marketing executives discuss how a modern data stack enables enterprises to meet customer expectations and drive results.

Any (functioning) system is built upon an infrastructure. This infrastructure supports all of the functions and activities of the system. Testing is no exception. With a good test infrastructure, QA teams can speed up their testing efforts and drastically improve efficiency. In this article, we will explore the concept of test infrastructure, and how you can effectively build one.

Generative AI (GenAI) has taken the world by storm, promising to revolutionize industries and transform the way businesses operate. From generating creative content to automating complex tasks, the potential applications of GenAI are vast and exciting. However, implementing GenAI in an enterprise setting comes with its own set of challenges. At Cloudera, we understand the complexities of enterprise GenAI adoption.

API-database coupling vs. traditional multi-layered architectures: what’s the difference and why does it matter? The main difference between direct API-database coupling and multi-layered architectures is that the former allows the API to interact directly with the database, minimizing latency and complexity, while the latter uses multiple layers to separate concerns.

For enterprises, commercial use of AI is still in its early stages, and it’s a case of risk and reward, weighing up both and investigating the best way forward. Of course, there’s much to gain from the use of AI. Already, companies are providing better customer service, parsing complex information through natural language inputs, and generally making workflows faster.