Skip to main content

The 3 big problems with data and how to avoid them


The 3 big problems with data and how to avoid them

Register Now

You’re invited to attend the Beyond Big Data Webinar Series, a set of 5 Red Hat webinars. Read more about the entire series.

Webinar 1: The 3 big problems with data—and how to avoid them
November 5, 2014, 11:00 a.m. - 12:00 p.m.

No matter what your organization looks like, chances are you're wrestling with at least one of the following data challenges:
  • Data silos that are difficult to access when needed
  • Point-to-point integration that doesn't scale
  • Data sprawl leading to security and compliance risks
Join this webinar to learn how to implement a data strategy and architecture to avoid these problems.

Speakers:
Syed Rasheed, solution marketing manager, Red Hat
Syed Rasheed, solution marketing manager at Red Hat, coordinates marketing, evangelism, and consulting activities. In addition to helping customers address integration challenges, he is responsible for working with customers, partners, and industry analysts to ensure next-generation Red Hat technology meets customer requirements for building business process automation and integration solutions. Syed is an 18-year veteran of the IT industry with extensive experience in business process management systems, business intelligence, and data management technologies. His work spans several industries, including financial services, banking, and telecommunications.

Ken Johnson, director of product management, Red Hat
Ken Johnson, Red Hat director of product management, is responsible for SOA and data integration products and technologies. Prior to joining Red Hat, Ken was a senior engineering manager at MetaMatrix, Inc., a pioneer in the enterprise information integration (EII) market. He has also held technical leadership positions at Vignette Corporation, Oberon Software, and Sybase, Inc., with a focus on application integration and data management technologies.

Register Now

Comments

Popular posts from this blog

Teiid Runtimes Explained

If you have been following Teiid lately we have been going through a whole lot of renovations. Yes, renovations or reorganization or refactoring or whatever you want to call it. Basically, we are making Teiid more modular with fewer dependencies that can be used by however your use case dictates rather than use it as one monolith application deployed into WildFly JEE Application Server. There is nothing wrong in using Teiid as server model, but with the proliferation of container-based workloads and cloud-based architectures, the previous server-based model does not work or simply won't scale. So, we needed to think of alternatives, thus Teiid team introduced a couple different versions modular Teiid what we are calling as "Teiid Runtimes".

Note that in these modular Teiid runtimes, not all the features you were used to using in Teiid Server model may not be there but you will have extensions to add in those that are most appropriate for your domain. If you are looking …

Teiid Platform Sizing Guidelines and Limitations

Users/customers always ask us about the sizing of their Data Virtaulization infrastructure based on Teiid or the JDV product from Redhat. Typically this is very involved question and not a very easy one answer in plain terms. This is due to fact that it involves taking into consideration questions like:
What kind of sources that user is working with? Relational, file, CRM, NoSQL etc.How many sources they are trying to integrate? 10, 20, 100?What are the volumes of data they are working with? 10K, 100K, 1M+?What are the query latency times from the sources? How you are using Teiid to implement the data integration/virtualization solution. What kind of queries that user is executing? Even small federated results may take a lot of server side processing - especially if the plan needs tweaking.Is materializing being used?Is query written in optimal way?and so on..Each and every one of the question affects the performance profoundly, and if you got mixture of those then it become that much…