OVERVIEW

A financial services company wanted to rapidly develop a transactional portal for storing customer financial data and make the data available to customer service personnel.

PROBLEMS / CHALLENGES

The organization had made significant investments in its digital platforms and business optimization efforts but needed to streamline processes (such as allowing the customer service organization to access client records).  

In a microservices architecture, multiple technologies are physically separated by a network and communicate with each other. For the end user, microservices create a seamless user experience. As a technology, microservices enable service level scaling and reduce infrastructure costs.  Of course, poorly integrated systems can undermine these benefits resulting in data loss and integrity issues

The organization wanted to switch from their existing technologies to a modern microservices architecture. The new solution would be based on Salesforce.com, Cloudlanding.com, Amazon Web Services (AWS), and other platforms. The goal was to enable greater efficiency, and scalability, as well as reduce maintenance and support costs.

From a business perspective, the goal was maximum flexibility and versatility with as little code as possible.

APPROACH

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.  Services implemented were built on top of an AWS cloud architecture utilizing the following components:

  • AWS
    • AWS Elastic Beanstalk – Rails & RoR services
    • AWS Lambda – Clojure, Python
    • AWS EC2 – Java
  • Salesforce.com
  • Cloudlanding.com
  • Microservices 
    • ReactJS frontend
    • Registration
    • Customer Dashboard
    • Bank Verification
    • State machine (decides what is the current step and what is next)
    • Email/SMS Sender
    • Live Chat
    • Contract Generator

The financial portal takes login, user profile, transactions, notifications, and other reports as separate services defined by the business functionalities.

The approach for this project was all about flexibility and pairing the right tools to each microservices integration.  The goal is to achieve the most flexible and scaleable microservices architecture.

OUTCOME

The modernized, scalable solution uses microservices, has a high fault tolerance, and can be infinitely scaled as the company grows. More specifically, through the use of microservices, agile methodologies, and DevOps, applications are being created faster. In fact, deploying hotfixes (which used to take days) is now completed in just a few hours.  The solution was implemented with no incidents.

Understand the trade-offs of technical debt

How do you strike the right balance between feature development and the handling of technical debt? New white paper now available.

Talk to the team that worked on this project

Related Case Studies & Resources

Continuity of User Experience – Case Study

Continuity of User Experience – Case Study

Founded in 2010, 90Seconds is a video authoring platform that simplifies the complexity of video production, connecting brands to freelance creators through a simple, streamlined workflow. User experience background 90Seconds has three key user roles in...

Introducing Jira Software 8.0

Jira Software 8.0 is the next chapter of Jira for enterprise teams, harnessing a speedy new engine built for scale. With this release, Jira users will be able to communicate updates and priorities more clearly, while system administrators will find it easier and less...

Case Study: Loan Approval Workflow

Case Study: Loan Approval Workflow

CreditNinja is a fast-growing web loan application and approval service. It requires a loan approval workflow and high-quality solutions and fast code delivery to keep rapid development. 3rd party services needed to be efficiently integrated in order to fetch and...

Case Study: Accelerated Mobile Development

Case Study: Accelerated Mobile Development

The client needed help building mobile products on an accelerated timeframe OVERVIEW Sphere was asked to build a mobile application that allows employees to pay for a taxi using a corporate account.  The goal was to build a MVP within 3 months that shares 90%+ or more...

The rise of Kotlin and the decrease of technical debt

The rise of Kotlin and the decrease of technical debt

By Herman Kononets Kotlin is a programming language for the Java Virtual Machine that’s able to be used in any scenarios that currently utilize Java. Kotlin is quickly replacing Java as the preferred language for programming Android applications and functions. For...

Hiring A-Players

Hiring A-Players

Every company wants to hire people who have the talent, skills and drive to make the company successful. Recognizing top performers is key for any business, be it a start-up or an enterprise. You need to be the best version of yourself to excel in any industry. Many...

CTO vs COO?  What’s the Difference in a Technology Company?

CTO vs COO? What’s the Difference in a Technology Company?

CTO vs COO? What's the difference? We sponsor TechDebates.org because we believe strongly in the idea of sharing experiences and ideas. For centuries, people have used stories to pass on knowledge. I personally believe successful tech leaders have an obligation to...

Previous

Next