Scalable database, Scalable language @ JDC 2013

2. Maciek Próchniak
Algebraic topology
hocolim
Group cohomology
Monads
GWT
TouK
Camel
OSGi
CQRS
Scala
OrientDB

4. Poland, Egypt?
USA is scared :)

5. scalable database
OrientDB
scalable language
Scala

6. " ... a general purpose programming language
designed to express common programming patterns
in a concise, elegant, and type-safe way"
Scala about Scala

7. Potential client about Scala
"tiny market share and require a
very specific type of developers, which is more
likely to be found in an academic, rather than
business environment"

8. OrientDB about OrientDB
"... an Open Source NoSQL DBMS with both the
features of Document and Graph DBMSs.
"... written in Java and it's amazing fast: can store
up to 150,000 records per second on common
hardware"

9. Potential client about OrientDB
"OrientDB is another experimental product which
is closely tied to European academia,
much like Scala"
"Moreover, choosing a document-oriented
database for a typical business/commercial
application is simply
an architectural mistake."

10. Really?

12. Oracle
MySQL
PostgreSQL
Mongo
Couch
Riak
Neo4J

13. Oracle
MySQL
PostgreSQL
Mongo
Couch
Riak
Neo4J
?

14. Oracle
MySQL
PostgreSQL
Mongo
Couch
Riak
Neo4J
OrientDB

15. What's the real difference?
● Architecture
● Data model
● Data access

16. What's the real difference?
● Architecture
● Data model
● Data access

17. Consistency
Partition
tolerance
Availability

18. P - do you really need it?

19. NoSQL is about scalability?
● Replication
● Sharding
- TBD

20. Need more consistency?
● Transactions
● Optimistic locking
● MVCC

21. NoSQL written in Java
● No additional software
● We all know how to tune JVM
... Don't we?

22. Architecture

23. Architecture - in memory

24. Architecture - embedded

25. Architecture - remote server
HTTP
Binary

26. memory/local/remote

27. Impact: testability
Unit
Functional
Integration
H2/??
Mock
DevBase

28. Impact: testability
Unit
Functional
Integration
memory:/local:
mock/memory:
local:/remote:

29. What's the real difference?
● Architecture
● Data model
● Data access

30. Meet our domain
Customer
Address
Customer
Email
Address
Branch
Email

31. How would you model that?
Address
Email
Branch Customer
1..*1..*
1..*

32. Aggregate - consistency boundary
Aggregate: A collection of objects that are
bound together by a root entity, otherwise
known as an aggregate root.

33. Aggregate
The aggregate root guarantees the
consistency of changes being made within the
aggregate by forbidding external objects from
holding references to its members.

34. Data model
Customer
Address
Customer
Email

35. Modification
Customer
Address
Customer
Email

36. Customer in OrientDB

37. When document is not enough

38. Data model
Customer
Address
Customer
Email

39. Customer
Modification
Address
Customer
Email

41. Graph - direct links
Customer Customer
Customer Customer

42. Documents
connected into
Graph

43. Connections in OrientDB

44. New possibilities
Europe
Poland France Romania
Warsaw Lublin Cracow Łódź

45. New possibilities
2012
Jan Feb March
1 2 3 4

46. OrientDB data model can
reflect your domain model
better than document
or relational bases

47. What's the real difference?
● Architecture
● Data model
● Data access

48. Let's get our hands dirty

49. Scala
● implicit conversions, parameters
● typeclasses
● for-comprehension
● infix notation
● case classes

50. Connecting - classic template

51. Connecting - classic - PROS
● Everybody knows it
● Simple
● Can easily do DI
● AOP

52. Composability?

53. Side effects?

54. Making DB interaction explicit
● Type constructor
trait WithConnection[T]

55. Making DB interaction explicit
● Trivial interaction
def pt[T](a:T) : WithConnection[T]

56. Making DB interaction explicit
● Composing interactions
def fmap[T](a:WithConnection[T],
map:T=>WithConnection[H]) :
WithConnection[H]

57. Example

58. Example

59. for-comprehension

60. Composition

61. for-comprehension

62. Don't want to scary you...
... but I smell a monad here!

63. Scala - loading documents

64. Browsing documents - POJSON

65. Browsing documents - POJSON

66. Updating records
update customer set name = 'Maciej'
where name = 'Maciek'
update customer add friends = #8:2
update customer put contactDetail =
'email2', 'mp@touk.pl'

67. Updating records - lens like

68. Updating records - lens like

69. Developers
know
SQL

70. ExtendedSQL
select from customer
where name = 'maciek'
select labels[0] from customer
where name = 'maciek'
select address.street from customer
where contactDetails.email = 'mproch@g.pl'

71. ExtendedSQL
select from customers where trucks
contains (capacity = 2)
select from suppliers where
trucks[capacity = 5].size() > 3

72. OrientDB
NotSoNoSQL

73. Scala queries

74. Graph queries

75. Developers
know
SQL

76. Traverse command
traverse customer.friends from #8:0
while $depth < 3
select from (
traverse customer.friends from
#8:0 while $depth < 10 )
where label contains nice

77. Traverse performance
Local operation - no joins
Constant lookup time

78. Traverse with scala predicates

79. Traverse with scala predicates

80. What about higher level access?
● ORM anybody?
● No need for partial updates, dirty checking?

81. JSON under the hood
Pluggable serialization strategies:
● Jackson
● Lift-Json
● ...

82. Scala serializer

83. Typesafe queries?
Scala
Language
Intergration
Connectivity
Kit

85. Lifted embedding

86. Lifted embedding - meta

87. Lifted embedding - meta

88. Lifted embedding - meta

89. Lifted embedding - query

90. Lifted embedding - query

91. Can we do better?

92. Direct embedding - meta

93. Direct embedding - query

94. Direct embedding - query

95. Type safety?

96. Functional Programming patterns
help to create
flexible, robust data access code

97. Call for action!
● Try it!
● Use it
● Find bugs ;)
● Spread the word

98. https://github.com/nuvolabase/orientdb/
https://github.com/mproch/scala-orientdb
https://github.com/mproch/slick-orientdb

99. Take away:
● OrientDB data model can reflect your
domain model better than document or
relational bases
● Functional Programming patterns can help
create flexible, robust data access code

100. ‫ﺷﻜﺮا‬

101. mpr@touk.pl
http://touk.pl
http://mproch.blogspot.
com

102. http://www.flickr.com/photos/prawnpie/133328694/