I was recently interviewed by Elise Greve of AWS about how we scaled Credit Genie from MVP to a full-scale platform with over 20 AWS Amplify applications. You can find the original article here. In this post I want to expand on some of the topics covered in that interview.
Who is Credit Genie?
Credit Genie is a Fintech company focused on helping 10 million consumers get out of credit card debt. We've partnered with one of the largest non-profit credit counseling organizations in the United States to provide a platform for Credit Counseling Agencies to provide debt relief to consumers struggling with credit card debt.
Credit Genie provides a SaaS-based customer servicing platform that enables Credit Counseling agencies to collect consumer financial data including income, expenses, and debt history in order to evaluate consumer financial health and offer needs-based debt management plans.
To achieve this, Credit Genie offers an online web application that allows a consumer to securely submit their financial information. Also, several web portals exist where the credit counselor and consumer can log in and view various financial-related information. The Credit Genie platform also integrates with several third-party systems such as TransUnion and Plaid to accurately confirm consumer financial information.
Credit Genie is Serverless-First, reaching for managed services to solve our business and technical problems. We believe that the future of software development and architecture is a cloud-based, serverless-first world where elasticity and pay-as-you-go are at the forefront.
We've also picked AWS to be our cloud provider and were early adopters of AWS Amplify to facilitate our web application development and cloud infrastructure provisioning needs. Leveraging Amplify has allowed us to go from MVP to a multi-account, single-tenant platform serving millions of requests per month in under a year. Amplify is used to orchestrate our AWS serverless footprint including AppSync, DynamoDB, Lambda, APIGW, S3, SQS, Cognito, Redshift, and more.
Building a SaaS-based solution within FinTech offers its own set of unique problems. At the forefront are security, scalability, and cost-effectiveness. We believe a shift-left approach on these 3 concerns, along with the adoption of serverless technologies is what defines a modern, well-architected FinTech platform.
Security within FinTech is a hot-button issue these days. A quick google search shows several high profile data breaches over the past 10 years.
Here at Credit Genie, we have 5 guiding principles for security.
Customer data must always be segregated. We have several counseling agencies servicing their customers on our platform, and it's important that each agency's customer data is isolated. The core idea here is to limit the blast radius if an incident were to occur.
Humans and services must adhere to the principle of least privilege. Humans and services will always need permissions to do things; there's no way around that. The principle of least privilege means that these actors only receive the minimal amount of access needed to fulfill the task.
Tasks performed by humans and services must be observable and auditable. Credit Genie leverages CloudWatch and CloudTrail to ensure that all compute services are monitorable and all AWS API requests are auditable.
All permission grants must be time-boxed. Whether a human or a service needs permissions to perform a task, they must re-authenticate within the context of each unit of work. In other words, no permanent authorization.
At Credit Genie, we “build today with tomorrow in mind,” meaning everything we build is designed to cater to current scale requirements as well as anticipated growth.
This is why we love AWS Amplify and Serverless in general. Every managed service we leverage in AWS has this same mantra baked into its design. AWS calls it this elasticity, but the general idea is that your services should be able to scale up/down/in/out as the load on the system changes over time.
Growth is fundamental to the success of a startup. Technology costs can be a wet blanket on growth if left unchecked. We design our systems with cost in mind from the start.
By always reaching for serverless and managed services in AWS first, we are getting elasticity in both scale and cost. AppSync, Lambda, S3, DynamoDB, Amplify, and CloudFront all follow on-demand, pay-as-you-go pricing models.
At its core, the Credit Genie platform is comprised of an Online Transactional Platform (OLTP) and an Online Analytical Platform (OLAP) and is all managed under a single AWS Organization.
The OLTP is a collection of single-tenant AWS accounts for each participating agency, with a few extra accounts to solve cross-cutting concerns like IAM and DNS. These environments service the day-to-day operations of the consumer and credit counselor like collecting and storing consumer data and facilitating credit counselor daily activities.
The OLAP consists of a data warehouse in RedShift and S3 via Spectrum and an Airflow cluster managing numerous ETL workflows. The OLAP also enables our data scientists, analytics, and business intelligence experts to do what they do best.
Let's step through this architecture diagram.
Customers are funneled to a single URL, which is a CloudFront distribution with a Viewer Request Lambda@Edge.
The Viewer Request Lambda@Edge intercepts every URL visit and determines which participating agency will receive the customer; ultimately redirecting the customer to the agency Amplify application URL. Think of this as a traffic router. From this point, the customer completes the online application within the agency isolated AWS Amplify application, allowing for physical separation of customer data across member agencies.
As customers are routed into isolated Amplify applications and submit their financial information, subsets of that data are streamed into a centralized data warehouse in AWS RedShift. This enables our Reporting, Analytics, and Data Science teams to perform analysis and business intelligence on all sorts of dimensional data sets.
DNS management with a multi-account single-tenant architecture can be tricky. Our solution involves having a dedicated AWS account with the single responsibility of managing all DNS records via Route53.
Identity and Access Management is also a complex problem to solve in this type of architecture. We lean heavily on AWS Organizations and SSO to manage all of our internal AWS Users, Roles, and Permission Sets.
How do new features get introduced in architecture like this? We have a single repository with several branches. Features are merged into our main branch which triggers the development environment's build, test, and deploy steps. If successful, the main branch is merged into a pre-production environment where all the same checks are run one more time. Finally, changes are merged into several customer environments and deployed into production.
Our Scale So Far
The following charts span the 10 months between August 2020 to May 2021 during which our platform scaled from 3 to 15+ environments. In general, we've seen steady growth over the past 10 months as we've onboarded more and more Credit Counseling Agencies.
AppSync requests/month increased from ~1.8 to ~6.2 million requests per month.
Lambda GB-seconds increased from ~0.5 to ~2 million GB-seconds per month.
Amplify Build usage increased from ~2 to ~4 thousand minutes per month.
S3 storage increased from ~400 to ~900 GB per month
AWS operates under the Shared Responsibility Model. At a high level, this means that AWS guarantees the infrastructure, but it's up to you to responsibly drive and navigate it.
Our growth would not be possible without our amazing team of drivers, navigating AWS like the NASCAR champs that they are (sorry for the cheesy metaphor gang). I would be remiss to not mention each one of them here. Connect with all of these amazing engineers!
Wrapping Things Up
Thank you so much for reading through our technology journey over the past 10 months. AWS and Serverless technologies are very powerful tools for solving your security, scaling, and cost problems and I hope this article helps you navigate your own AWS adventures!
If you enjoyed this, follow me over on Twitter!
Did you find this article valuable?
Support Alex Kates by becoming a sponsor. Any amount is appreciated!