Highly Scalable Microservices
Transaction Portal for a FinTech Company
- Industry
- Financial Services
- Service
- Microservices Architecture|AWS Cloud Engineering|Salesforce Integration|DevOps & Continuous Delivery
Overview
A financial services company wanted to rapidly develop a transactional portal for storing customer financial data and making it available to customer-service personnel. The organization had made significant investments in its digital platforms and business-optimization efforts but needed to streamline how its customer-service team accessed client records.
The goal was to switch from existing legacy technologies to a modern microservices architecture built on Salesforce.com, Cloudlanding.com, AWS, and other platforms — unlocking efficiency and scalability while cutting maintenance and support costs. From the business side: maximum flexibility and versatility with as little code as possible.
How We Solved It
Sphere’s developers embraced simplicity because simplicity is a prerequisite for reliability. The goal was code that is easy to understand, easy to change, and easy to debug. The architecture broke the portal into independently scalable services and paired the right tool to each:
1. AWS Cloud Foundation
Services were built on top of an AWS cloud architecture, with each runtime chosen for its workload: AWS Elastic Beanstalk for Rails & RoR services, AWS Lambda for Clojure and Python functions, and AWS EC2 for Java workloads. The result is service-level scaling, isolated failure domains, and reduced infrastructure cost.
2. Microservices Catalog
The portal exposes login, user profile, transactions, notifications, and other reports as separate services defined by business functionality — Registration, Customer Dashboard, Bank Verification, a State Machine that drives the next step, Email/SMS Sender, Live Chat, and Contract Generator. Each service can be deployed, scaled, and upgraded independently.
3. ReactJS Front-end + Salesforce / Cloudlanding
A ReactJS front-end gives the customer-service organization a fast, modern interface, while Salesforce.com and Cloudlanding.com handle CRM and origination workflows. The integration was kept thin — flexibility and versatility were prioritized over framework lock-in.
Key Outcomes
Hotfixes in Hours, Not Days
Through microservices, agile delivery, and DevOps, deploying hotfixes — which used to take days — is now completed in just a few hours.
High Fault Tolerance
The modernized solution isolates failure domains across services, so issues in one component no longer cascade across the customer experience.
Infinitely Scalable
The architecture scales horizontally per service, ready to grow with the company without re-platforming.
Zero-Incident Rollout
The cut-over from the legacy stack to the new microservices platform was implemented with no incidents in production.
The Results
The modernized, scalable solution uses microservices, has a high fault tolerance, and can be infinitely scaled as the company grows. With agile methodologies and DevOps in place, applications are now created faster, and what used to be a multi-day hotfix is delivered in hours — without operational drama.
