Scaling applications and production systems
The systems became larger, more connected, and more operationally demanding. I took broader responsibility for architecture across reporting platforms, integrations, cloud infrastructure, and long-running production applications, while continuing to write core application code. I also helped a distributed development team break down, review, and deliver increasingly complex work.
How I put them to work
- Financial reporting: I helped maintain and extend a reporting portal for an Atlanta correspondent bank that served more than 100 banks every week for seven years. Customers uploaded Excel files that we mapped to database tables and processed into bond accounting, borrowing and SWAP reports, alongside a set of accounts-receivable conversion calculators.
- Donor portal and pledge drives: I developed a donor portal and pledge-drive management system handling one-time, recurring and pledge gifts, with administrative dashboards and CRM and payment integrations. It served more than 2,000 donors a year and processed over $1 million in donations.
- Guided selection: I built a wizard for a manufacturing parts supplier that walked customers to the right part through a series of questions, preserving state and validating complex choices without exposing the complexity behind it.
- Shopify integration: I synchronized data through Shopify APIs and GraphQL, then used its JavaScript API to assemble carts and hand users into checkout.
- Cloud migration and operations: I built and maintained an Elastic Beanstalk environment that scaled up through pledge-drive peaks and back down afterwards, then planned and carried out the move of every customer off our own data center and into AWS, across EC2, VPCs, EBS, EFS and RDS, improving estimated availability from roughly 98% to about 99.9%. I designed the topologies for availability and redundancy and ran day-to-day operations, including Ubuntu, Apache and MySQL changes and incident response, with contractors doing the server build-out itself.