Skip to content
GigaSpaces Logo GigaSpaces Logo
  • Products
    • InsightEdge Portfolio
      • Smart Cache
      • Smart ODS
      • Smart Augmented Transactions
    • GigaSpaces Cloud
  • Roles
    • Architects
    • CXOs
    • Product Teams
  • Solutions
    • Industry Solutions
      • Financial Services
      • Insurance
      • Retail and eCommerce
      • Telecommunications
      • Transportations
    • Technical Solutions
      • Operational BI
      • Mainframe & AS/400 Modernization
      • In Memory Data Grid
      • Transactional and Analytical Processing (HTAP)
      • Hybrid Cloud Data Fabric
      • Multi-Tiered Storage
      • Kubernetes Deployment
      • Streaming Analytics for Stateful Apps
  • Customers
  • Company
    • About GigaSpaces
    • Customers
    • Partners
    • Support & Services
      • University
      • Services
      • Support
    • News
    • Contact Us
    • Careers
  • Resources
    • Webinars
    • Blog
    • Demos
    • Solution Briefs & Whitepapers
    • Case Studies
    • Benchmarks
    • ROI Calculators
    • Analyst Reports
    • eBooks
    • Technical Documentation
  • Contact Us
  • Try Free

Default configuration may not be best for my demo…

Subscribe to our blog!

Subscribe for Updates
Close
Back

Default configuration may not be best for my demo…

Owen August 3, 2007
1 minutes read

Last night I spoke at the Dusseldorf JUG and had a very nice time with one exception: I broke my last demo. YIPE!
I have suffered for hours since then going over my code and trying to see where I dropped the ball and finally, looking elsewhere, have come upon the reason!
The default setting for replication in the cluster configuration that I selected for the demo in GigaSpaces 6.0 XAP is sync-rec-ack. sync-rec-ack defines the replication behavior to be ‘nearly synchronous’ with the client thread blocking only long enough to ensure that the request has been sent – not received – by the backup space.
I changed the setting to fully synchronous – called ‘sync’ in our configuration, and things are much much better. Now, I understand how Virgin Mobile succeeded with our technology where I failed. (they use the sync setting).
For those of you who were watching, my apologies for losing that one order when I killed both of the primary spaces as it was running. With this new improvement, I swear it won’t happen again!
Cheers,
Owen.

CATEGORIES

  • Caching
  • GigaSpaces
  • Java
  • sba
Owen

All Posts (36)

YOU MAY ALSO LIKE

December 19, 2007

Get some “space” over the…
2 minutes read

May 13, 2009

Benchmarking on the Cloud –…
16 minutes read

November 12, 2015

Building a dynamic high-speed data-hub…
8 minutes read
  • Copied to clipboard

PRODUCTS, SOLUTIONS & ROLES

  • Products
  • InsightEdge Portfolio
    • Smart Cache
    • Smart ODS
    • Smart Augmented Transactions
  • GigaSpaces Cloud
  • Roles
  • Architects
  • CXOs
  • Product Teams
  • Solutions
  • Industry
    • Financial Services
    • Insurance
    • Retail and eCommerce
    • Telecommunications
    • Transportation
  • Technical
    • Operational BI
    • Mainframe & AS/400 Modernization
    • In Memory Data Grid
    • HTAP
    • Hybrid Cloud Data Fabric
    • Multi-Tiered Storage
    • Kubernetes Deployment
    • Streaming Analytics for Stateful Apps

RESOURCES

  • Resource Hub
  • Webinars
  • Blogs
  • Demos
  • Solution Briefs & Whitepapers
  • Case Studies
  • Benchmarks
  • ROI Calculators
  • Analyst Reports
  • eBooks
  • Technical Documentation
  • Featured Case Studies
  • Mainframe Offload with Groupe PSA
  • Digital Transformation with Avanza Bank
  • High Peak Handling with PriceRunner
  • Optimizing Business Communications with Avaya

COMPANY

  • About
  • Customers
  • Management
  • Board Members
  • Investors
  • News
  • Events
  • Careers
  • Contact Us
  • Book A Demo
  • Try GigaSpaces For Free
  • Partners
  • OEM Partners
  • System Integrators
  • Value Added Resellers
  • Technology Partners
  • Support & Services
  • University
  • Services
  • Support
Copyright © GigaSpaces 2021 All rights reserved | Privacy Policy
LinkedInTwitterFacebookYouTube

Contact Us