Case Study: Cloud Server support for Events.com
Spingo.com originally an independent events management platform was consumed by Events.com. SpinGo’s infrastructure was complex and under strain. A mix of deprecated systems (like “Engine” and “Q”), redundant data pathways, and fragile server dependencies introduced instability and inefficiency.
Feel free to reach out to Dave and say hi or check out our case studies for some examples of our work.
The Challenge
Unstable Legacy Systems Caused Service Disruptions: Deprecated tools like “Engine” and redundant services like “Q” introduced frequent crashes, slowdowns, and unclear data routing.
Data Sync Failures and Inconsistencies: Salesforce integration, venue records, and approval flows suffered from syncing issues, leading to duplicate or inaccurate data.
Manual Deployments Increased Risk of Downtime: Code deployment and server provisioning relied heavily on manual processes, which were slow, error-prone, and hard to scale.
Inefficient Server Usage and Poor Resource Allocation: The existing setup lacked optimization, leading to wasteful usage, inconsistent uptime, and unreliable performance during peak traffic.
Our Solution
Inefficient AWS Usage and Poor Resource Allocation: The existing AWS setup lacked optimization, leading to wasteful usage, inconsistent uptime, and unreliable performance during peak traffic.
Automated CI/CD with Jenkins and Salt-Stack: Built automated deployment pipelines that cut out manual steps, improved release speed, and reduced human error.
Monitoring and Self-Healing Systems: Integrated CloudWatch, automated recovery processes, and centralized logging to proactively detect and fix issues.
Service Consolidation and Cleanup: Retired outdated services like “Engine” and merged overlapping functionality into more stable systems like “Q” for simplicity and performance.
Tech Stack:
Results
99.99% Uptime Across All Production Services: Infrastructure remained highly stable even during large traffic spikes and promotional events.
Faster, More Reliable Deployments: CI/CD pipeline reduced deployment time and improved overall engineering velocity.
Improved System Reliability and Data Integrity: Salesforce and venue syncs now operate smoothly, reducing QA overhead and support tickets.
Lower DevOps Overhead and Freed-Up Engineering Resources: Internal teams could focus on building features instead of fighting fires, thanks to automation and Basebuild’s ongoing DevOps support.