Download - [OracleCode - SF] Distributed caching for your next node.js project

Transcript
Page 1: [OracleCode - SF] Distributed caching for your next node.js project

Distributed Caching for Your

Next Node.js Project

Page 2: [OracleCode - SF] Distributed caching for your next node.js project

@gamussa @hazelcast #oraclecode

Solutions ArchitectDeveloper Advocate@gamussa in internetz

Please, follow me on TwitterI’m very interesting ©

> whoami

Page 3: [OracleCode - SF] Distributed caching for your next node.js project

@gamussa @hazelcast #oraclecode

Why cache?

Page 4: [OracleCode - SF] Distributed caching for your next node.js project

@gamussa @hazelcast #oraclecode

Page 5: [OracleCode - SF] Distributed caching for your next node.js project

@gamussa @hazelcast #oraclecode

Page 6: [OracleCode - SF] Distributed caching for your next node.js project

@gamussa @hazelcast #oraclecode

Business Application (instance 2)

Business Application (instance 1)

Service Service Service

RDBMS Mainframe MongoDBNoSQL REST

Page 7: [OracleCode - SF] Distributed caching for your next node.js project

@gamussa @hazelcast #oraclecode

Page 8: [OracleCode - SF] Distributed caching for your next node.js project

@gamussa @hazelcast #oraclecode

Cache is good for…◇Performance ◇Offload expensive parts of your architecture◇Scale up – get the most out of one machine

Page 9: [OracleCode - SF] Distributed caching for your next node.js project

@gamussa @hazelcast #oraclecode

Page 10: [OracleCode - SF] Distributed caching for your next node.js project

@gamussa @hazelcast #oraclecode

Cache is good for…◇Performance ◇Offload expensive parts of your architecture◇Scale up – get the most out of one machine◇Scale out – add more capacity with more machines

Page 11: [OracleCode - SF] Distributed caching for your next node.js project

@gamussa @hazelcast #oraclecode

Page 12: [OracleCode - SF] Distributed caching for your next node.js project

@gamussa @hazelcast #oraclecode

Cache is good for…◇Performance ◇Offload expensive parts of your architecture◇Scale up – get the most out of one machine◇Scale out – add more capacity with more machines◇Usually very fast and easy to apply

Page 13: [OracleCode - SF] Distributed caching for your next node.js project

@gamussa @hazelcast #oraclecode

Page 14: [OracleCode - SF] Distributed caching for your next node.js project

@gamussa @hazelcast #oraclecode

Polyglot planform

@gAmUssA @hazelcast #jfokus #hazelcastjet

Problem

Data doesn’t fit just one machine

Page 15: [OracleCode - SF] Distributed caching for your next node.js project

@gamussa @hazelcast #oraclecode

What’s

Page 16: [OracleCode - SF] Distributed caching for your next node.js project

@gamussa @hazelcast #oraclecode

Page 17: [OracleCode - SF] Distributed caching for your next node.js project

@gamussa @hazelcast #oraclecode

Replication or Sharding?

http://book.mixu.net/distsys/single-page.html

Page 18: [OracleCode - SF] Distributed caching for your next node.js project

@gamussa @hazelcast #oraclecode

Demo time!It’s #oraclecode!Show me some code, yay!

Page 19: [OracleCode - SF] Distributed caching for your next node.js project

@gamussa @hazelcast #oraclecode

http://hazelcast.github.io/hazelcast-nodejs-client/

Page 20: [OracleCode - SF] Distributed caching for your next node.js project

@gamussa @hazelcast #oraclecode

Thanks!Any questions?You can find me at:◇@gamussa◇[email protected]