Orchestrate COO Matthew Heitzenroder takes you

1. Too Many Databases,
Not Enough Data

2. Matt Heitzenroder
@roder

3. EMEA General Manager
and Managing Director

4. Cofounder and COO

5. Anyhow…
Too Many Databases,
Not Enough Data

6. DATABASES

7. 2000s 1990s 1980s

8. Which database do
you choose?

9. 1
23
4
5

10. Why?

12. Why are so many
“best tools” for the
job?

14. Queries
Operations

15. Queries
Operations

16. Operations
Queries

17. Queries
Operations

18. and MySQL?

20. So…. again… Why are so
many “best tools” for the
job?

21. NoSQL databases are
optimized for specific
types of queries and
operational characteristics.

22. Where is the
Operational Simplicity
with FIVE DATABASES?

24. Primary Key
Secondary Index
Full-Text Search
Time-Series
Graph/Relational
Geospatial

26. Orchestrate exposes the
querying features of
many types of databases
through a REST API

27. As-a-service, developers
and operations engineers
are not constrained by
server resources (CPU,
RAM, I/O)

28. Primary Key
Secondary Index
Full-Text Search
Time-Series
Graph/Relational
Geospatial

29. 1
23
45
*Klout not a customer - example only

31. Where else?
Any where you want

32. HBase
Lucene*
Titan*
MySQL
Kafka

33. PubSub
Geospatial
Stream Processing

34. hello@orchestrate.io