8. an open-source project
8
leading open-source in-memory data
grid.
Apache 2 License
dead simple distributed programming
lightweight w/o any dependency
built with in Istanbul
45. 45
Great for early stages of rapid
application development and iteration
Necessary for scale up or scale out
deployments – decouples
upgrading of clients and cluster for
long term TCO
Embedded Hazelcast
Hazelcast Node
1
Applications
Java API
Client-Server Mode
Hazelcast
Node 3
Java API
Applications
Java API
Applications
Java API
Applications
Hazelcast
Node 2
Hazelcast
Node 1
Hazelcast Node
2
Applications
Java API
Hazelcast Node
3
Applications
Java API
Deployment Options
48. 48
Data Store Features
Java Collection API: Map, List, Set, Queue
JCache
High Density Memory Store
Hibernate 2nd Level Cache
Web Session Replication: Tomcat, Jetty
Predicate API: Indexes, SQL Query
Persistence: Map/Queue Store & Loader. Write Behind/Through
Eviction
Near Cache
Transactions: Local & XA
WAN Replication
Memcached Interface
49. 49
Distributed Computing Features
Java Concurrency API
(Lock, Semaphore, AtomicLong, AtomicReference, Executor Service, Blocking Queue)
Entry and Item Listeners
Entry Processor
Aggregators
Map/Reduce
Data Affinity
Continues Query
Map Interceptors
Delta Update
51. Spring Cache Manager
Hibernate 2nd Level Cache Provider
Web Session Replication
OSGI Support
51
Hazelcast Integration
Modules
52. Management Center (free up to 2 nodes)
High-Density Memory
Tomcat/Jetty Session Replication
Enterprise WAN Replication
Security
Native Clients (.NET/C++)
52
Hazelcast Enterprise
Features
53. Thank you ! :)
emrah@hazelcast.com
53
any questions ?
I’ve joined the team one and a half year ago.
teb-bnp paribas joint venture
android
enterprise
Anyone used it before?
Anyone heard it before?
Hazelcast is an operational in-memory computing platform that lets companies manage data and distribute processing using in-memory storage and parallel execution for breakthrough application speed and scale.
it is under apache 2 license so you can fork hazelcast and develop your own features or product,
it is just 1 jar..
-So, How do we survive as a company?
We develop enterprise features such as high density memory. So you can put huge amount of data to native memory which is not under control JVM.
Another example can be SSL support.. (security feature)
- Management Center after 2 Nodes
Also we open sourced our clients.
Going beyond “normal amounts of data” and “normal amounts of users”
This is possible with two ways: Scale up vs. Scale out
Scale up: Better hardware
Scale out: Cluster/Distribute
Bruce Banner :)
Choose between fighting one horse-sized duck and 100 duck-sized horses
Scale up: Cons->PRICE, Greater risk of hardware failure causing bigger outages, generally severe vendor lock-in and limited upgradeability in the future.
Scale out: Pros-> Much cheaper than scaling vertically, Easier to run fault-tolerance, Easy to upgrade.
L1 - There is a sandwich in front of you.
L2 - Walk to the kitchen and make a sandwich
RAM - Drive to the store, purchase sandwich fixings, drive home and make sandwich
HD - Drive to the store. Purchase seeds. Grow seeds..... .... ... Harvest lettuce, wheat, etc. Make sandwich.
In Hazelcast, every data is stored in a partition. And partitions are stored in nodes… There are 271 partitions as default, and every node has information about which partition is stored in which node.