On October 23rd, 2014, we updated our
By continuing to use LinkedIn’s SlideShare service, you agree to the revised terms, so please take a few minutes to review them.
Today’s Reality – Tier Based Architecture Separate technology implementation Separate technology implementation bottlenecks bottlenecks Separate technology implementation Bottlenecks in all areas where state is stored, architecture can’t scale linearly!
Traditional Architecture - path to complexity…A Auction ServiceB Bid Service Auction Bid Trade InfoT Trade Service A B T I I Process Service Bid Service Service Service Bid Result ResultI Info Service Bid Validate Process Accepted TradeT Timer Service Place bid Bidder Get Bid Result Auction Timer Owner T Service
Traditional Architecture - path to complexity…A Auction ServiceB Bid ServiceT Trade Service A B T II Info ServiceT Timer Service Business tier Bidder Auction Owner Back-up Separate failover strategy and implementation for each tier Redundancy doubles network traffic Bottlenecks are created Back-up Latency is increased
Do you see the Problem?Scalability is not linear Business tierScalability management B nightmare I A B T Bidder Auction Owner Back-up Back-up Back-up Back-up
The SolutionGigaSpaces Elastic Application Server
Step 1 – Create a Processing UnitA Auction ServiceB Bid Service B T I AT Trade ServiceI Info Service Processing UnitT Timer Service Business tier Bidder Auction Owner Single model for design, deployment and management No integration effort Manage data in memory Collapse the tiers Collocate the services
Step 2 – Async PersistencyA Auction ServiceB Bid Service B T I AT Trade Service Place BidI Info ServiceT Timer Service Processing Unit Validate Bidder Process Bid Auction Owner Get Bid Process Trade Results Process Results Persist for Compliance & Collocation of data, messaging Reporting purposes: and services in memory: - Storing State Minimum Latency (no - Register Orders network hops) - etc. Maximum Throughput
Step 3 – Resiliency SLA Driven Backup Container B T I B T I A A Processing Unit Single, built-in failover/redundancy investment strategy Fewer points of failure Automated SLA driven failover/redundancy mechanism Continuous High Availability
Step 4 – Scale Backup Backup B T I B T I B T I B T I A A A A 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
Step 5 – Auto Scale Out
The Processing Unit – Scalability UnitSingle Processing Unit Processing Unit - Scaled Involves Config Change No code changes!
The Processing Unit – High-Availability Unit Primary - Processing Unit Backup - Processing Unit Business logic – Active mode Business logic – Standby mode Sync Replication
The Processing Unit - Database Integration Primary - Processing Unit Backup - Processing Unit Business logic – Active mode Business logic – Standby mode Sync Replication Async Async Replication Replication Initial Load Mirror Process ORM