Technology Category
- Application Infrastructure & Middleware - Middleware, SDKs & Libraries
The Customer
Concur
About The Customer
Concur is a leading provider of integrated travel and expense management solutions. Their cloud services process over $50 billion in travel and expense spend per year for global corporations.
Concur was founded in 1993 on the premise of helping to drive
The Challenge
Concur is a leading provider of integrated travel and expense management solutions for companies of all sizes. As a leading SaaS provider, Concur constantly seeks to improve scalability and performance across their architecture and infrastructure stack especially the database and storage tiers.
Initially, Concur utilized a homegrown caching system that turned out to be expensive and complicated to scale. They wanted to replace it with an open source solution that could help laterally scale their application, and provide the resilience and redundancy they needed with simplicity and efficiency. They also wanted the new solution to support their aggressive plans for using NoSQL technology extensively throughout their stack in the future.
The Solution
Concur implemented a large Couchbase Server cluster, utilizing the Enyim (.NET) client for the web tier and the spymemcached (Java) client for the middle tier. They were impressed with the simplicity with which they could setup, configure and scale the cluster.
Couchbase's cluster management capabilities give Concur the ability to scale out their cluster with zero downtime. They also get the added benefit zero configuration management when adding or removing nodes from their cluster because both the .NET and Java clients are automatically updated when there is a topology change, ensuring smooth and consistent growth of the Couchbase cluster across the entire environment.
Couchbase's cluster management capabilities give Concur the ability to scale out their cluster with zero downtime. They also get the added benefit zero configuration management when adding or removing nodes from their cluster because both the .NET and Java clients are automatically updated when there is a topology change, ensuring smooth and consistent growth of the Couchbase cluster across the entire environment.
Operational Impact
Quantitative Benefit
Case Study missing?
Start adding your own!
Register with your work email and create a new case study profile for your business.