GigaSpaces Clustering

2

Today’s Reality – Tier Based Architecture Separate technology implementation

Bottlenecks in all areas where state is stored, architecture can’t scale linearly!

Separate technology implementation

Separate technology implementation

bo

ttle

nec

ks

bo

ttle

nec

ks

3

AuctionOwner

Traditional Architecture - path to complexity…

Auction Service

Bid Service

Trade Service

Place bid

Info Service

Timer Service

Auction

Service

Bid

Service

Trade

Service

Info

Service

Timer

Service

B T I

A

B

T

I

T

TT

AA BB TT II

Bidder

Validate

Result

ProcessBid

Bid Accepted

Bid Result

Process Trade

Get Bid Result

4

Traditional Architecture - path to complexity…

4

Business tier

Back-up

Back-up

Redundancy doubles network traffic

Bottlenecks are created

Latency is increased

Separate failover strategy and implementation for each tier

Bidder

AuctionOwner

Auction Service

Bid Service

Trade Service

Info Service

Timer Service

A

B

T

I

T

AA BB TT II

5

BB

Do you see the Problem?

5

Business tierScalability is not linear

Scalability management nightmare

Back-upBack-up

Back-upBack-up

AA BB TT

II

Bidder

AuctionOwner

6

The SolutionGigaSpaces Elastic Application Server

7

AB T I

Step 1 – Create a Processing Unit

7

Business tier

Processing Unit

Single model for design, deployment and management

No integration effort

Manage data in memory

Collapse the tiers

Collocate the services

Auction Service

Bid Service

Trade Service

Info Service

Timer Service

A

B

T

I

T

Bidder

AuctionOwner

8

AB T I

Step 2 – Async Persistency

8

Processing Unit

Validate

Process Bid

Process Trade

Process Results

Place Bid

Get Bid Results

Persist for Compliance & Reporting purposes:

- Storing State- Register Orders- etc.

Collocation of data, messaging and services in memory:

Minimum Latency (no network hops)

Maximum Throughput

Auction Service

Bid Service

Trade Service

Info Service

Timer Service

A

B

T

I

T

Bidder

AuctionOwner

9

AB T I

Step 3 – Resiliency

Processing Unit

Single, built-in failover/redundancy investment strategy

Fewer points of failure

Automated SLA driven failover/redundancy mechanism

Continuous High Availability

SLA Driven Container

Backup

AB T I

10

Processing Unit

Step 3 – Resiliency

Automated SLA driven failover/redundancy mechanism

Continuous Availability

Self Healing Capability

SLA Driven Container

Backup

Single, built-in failover/redundancy investment strategy

Fewer integration points mean fewer chances for failure

BackupPrimary

11

Step 4 – Scale

11

Processing Unit

Write Once Scale Anywhere:

Linear scalability

Single monitoring and management engine

Automated, SLA-Driven deployment and management

­Scaling policy, System requirements, Space cluster topology

Backup

AB T I

AB T I

Backup

AB T I

AB T I

12

Step 5 – Auto Scale Out

13

The Processing Unit – Scalability Unit

Single Processing Unit Processing Unit - Scaled

Involves Config Change

No code changes!

14

The Processing Unit – High-Availability Unit

Sync Replication

Primary - Processing UnitBusiness logic – Active mode

Backup - Processing UnitBusiness logic – Standby mode

15

The Processing Unit - Database Integration

Sync Replication

Primary - Processing UnitBusiness logic – Active mode

Backup - Processing UnitBusiness logic – Standby mode

Mirror Process

ORM

Initial Load

Async Replication

Async Replication

16

ThankThank

You!You!