Supporting data science in an enterprise involves more than installing Jupyter notebooks or using cloud services. Too often, the focus is on technology when it should be on data. The goal is to build multi-use infrastructure that can support both past uses and new requirements. This session discusses design assumptions, design principles, and the data architecture and data management for multi-use infrastructure.
Target Audience: BI and analytics leaders and managers; data architects, modelers, and designers; architects, designers, and implementers; anyone with data management responsibilities who is challenged by recent changes in the data landscape
Prerequisites: A basic understanding of how data is used in organizations, application and platform architecture, data management concepts
The focus in our market has been on acquiring technology, and that ignores the more important part: the landscape within which this technology exists and the data architecture that lies at its core. If one expects longevity from a platform then it should be a designed rather than accidental architecture.
Architecture is more than just software. It starts with uses, and includes the data, technology, methods of building and maintaining, governance, and organization of people. What are design principles that lead to good design and data architecture? What assumptions limit older approaches? How can one modernize an existing data environment? How will this affect data management? This session will help you answer these questions.