structurally sound: how to tame your architecture
TRANSCRIPT
Twitter Tag: #briefr The Briefing Room
Reveal the essential characteristics of enterprise software, good and bad
Provide a forum for detailed analysis of today’s innovative technologies
Give vendors a chance to explain their product to savvy analysts
Allow audience members to pose serious questions... and get answers!
Mission
Twitter Tag: #briefr The Briefing Room
Topics
July: SQL INNOVATION
August: REAL-TIME DATA
September: HADOOP 2.0
Twitter Tag: #briefr The Briefing Room
Paradigm Shift
Ø Push vs Pull
Ø Access & Governance
Ø Stop the ETL Madness!
Twitter Tag: #briefr The Briefing Room
Teradata
Teradata is known for its analytics data solutions with a focus on integrated data warehousing, big data analytics and business applications
It offers a broad suite of technology platforms and solutions and a wide range of data management applications
Last year, Teradata announced QueryGrid, a data access layer that can perform analytics across multiple databases and Hadoop
Twitter Tag: #briefr The Briefing Room
Guest: Imad Birouty
Imad Birouty holds the position of Director of Teradata Product Marketing and is responsible for Teradata software and hardware products including the Teradata Database, Teradata Platform Family, Teradata QueryGrid, Teradata Unity, Tools and Utilities, and In-Database Analytics. Prior to this, Imad led the Product Management team responsible for the Teradata Platforms, setting product strategy and direction.
Gartner Perspec:ve
“We will abandon the old models based on the desire to implement for high-‐value analy9c applica9ons.”
Architecture Demand
• All “data” needs to be “available” to users across the enterprise “all” the “)me”.
• The integra)on of data needs to be driven and drivable by the user.
• The analy)cs across the enterprise will be driven based on user role. This mandates more security and integra9on of the same in the solu9on, across the different plaQorms.
Data Architecture Transforma:on
• Data is not duplicated or rather minimally duplicated in the solu:on.
• Analy:cs is executed across different layers, which means integra:on of data within the solu)on layers.
• Push down processing of query and data is needed in this solu:on architecture.
• Cloud driven back-‐end storage and publishing of reports / dashboards will be the in-‐demand architecture of today / tomorrow.
Ques:ons • What was the key driver from Teradata's perspec:ve to create the QueryGrid? • What is the compe::ve landscape from a solu:on selling perspec:ve? • Why do customers need more educa:on on this solu:on set? (What is the key set of frustra:ons that
users cannot explain and need more focused educa:on?) • What analy:c solu:ons can be supported with combina:on of Teradata DW, QueryGrid, Hadoop, SAS, R
and Tableau technologies? • Who are the key buyers from a customer or prospect viewpoint -‐ business users or technology innovators
or both? • What is the future move from a solu:on perspec:ve on QueryGrid? • What are the new features if you can share from a solu:on perspec:ve? • What does a QueryGrid POC look from an execu:on perspec:ve? • Is there a cloud-‐based plaQorm that is being driven from this architecture? • Are there security features that are new or does current LDAP execu:on provide the security support
needed? • Does Teradata work on query op:miza:on in other systems apart from Teradata, considering the unique
feature and cool feature perspec:ves for QueryGrid? • Any specific use case or problem addressed by this solu:on that we can discuss?
Twitter Tag: #briefr The Briefing Room
Upcoming Topics
www.insideanalysis.com
July: SQL INNOVATION
August: REAL-TIME DATA
September: HADOOP 2.0