Big Data is een hype. Je hoort er iedereen mee zwaaien als de Big Thing van vandaag en tot morgen. Ondanks deze Buzz is het voor ons technische mensen meer en meer een realiteit. Het zal weldra zijn vaste plaats hebben in onze gereedschapskist. In deze sessie bekijken we wat Big Data echt is en wat je moet weten om de Big Data vragen van je klant technisch te beantwoorden. Naast de betekenis, de verscheidene disciplines, een overzicht en architectuur gaan we ook een aantal technologieen kort van dichtbij bekijken. - Hadoop, de computing engine, de omgeving en al zijn sattelieten. - Neo4j, de graph database. - ElasticSearch, de search database.

2. Agenda
• What is Big Data?
• Technology Radar
• Technologies in scope.
• Architecture
• Wanted!
• Next steps.

3. The world of data is changing.

4. Data has a chaotic nature.

5. Big Data <> Big Data
Big Data == Big in Data.

6. Big Data = 4 V’s.

7. Volume = Dealing with the size.

8. Variety
=
Handling the multiplicity of types, sources and formats.

9. Velocity
=
Reacting to the flood of information
in the time required by the application.

10. Veracity
=
How can we cope with
uncertainty, imprecision, missing values or untruths.

11. Big Data 1.0
=
Building the capabilities to process large data
In support of their current operations
(efficiency improvement).

12. Big Data 2.0
=
What can I now do that I couldn’t do before, or do
better then I could do before.

13. Polyglot persistence
• Relational databases are not dead.
• Enterprises should expect multiple data-storage technologies for
different applications.
• Even for a single application, polyglot persistence is good.
• Do not replace one database solution with another to expect
wonders.

16. Technologies in the picture
• Hadoop and technologies build on top of it.
• ElasticSearch.
• neo4J.

17. Hadoop
• Apache Foundation
• Commercial solutions
• Hortonworks
• Cloudera
• MapR

20. And many more...

21. ElasticSearch
• Based on lucene.
• ElasticSearch is also the name of the company.
• Search, analyze and index in realtime.
• Distributed.
• High availability.
• Document-oriented.
• Schema free
• RESTful api

24. neo4j
• Graph database.
• Ideal for metadata and relationships.
• Not for large content.
• Not for large graphs.

27. Polyglot persistence
• Relational databases are not dead.
• Enterprises should expect multiple data-storage technologies for
different applications.
• Even for a single application, polyglot persistence is good.
• Do not replace one database solution with another to expect
wonders.

30. Next steps.

31. Learning and case study group.

32. I need datastores:
- Openstreetmap.
- NASA
- ....

33. Q&A