How BillEase balances Python microservice
summary
BillEase claims a reproducible Python microservice workflow: a boilerplate repo seeds new services, dependency lists live in a requirements folder, local dev rarely runs pip, and CI simply runs pip install and tox. Integration tests mock RabbitMQ and AWS but exercise a real database, able to spin up Postgres (and Redis when needed), with CI jobs averaging 2m30s. The result is fast delivery, measurable test integration, and fewer surprise failures.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 35:27Balancing dev vs stakeholder needs
- 37:55Developer tools & deps
- 40:05CI setup & testing
- 41:08Future language transitions
- 43:19100% code coverage with mocks
- 44:45Why devs love BillEase
related talks
40mPython microservices on PaaS done right
33mLessons learned building Python microservices
06mIgnite: How CI/CD helped us "Bill Pay team" to deliver features faster to customers
25mA microservices architecture with Python and Docker containers
44mPython in the MicroServices world
22mBuilding towards a holistic development service — Amjad Masad
34mPython Micro-service Architecture
30mHow To Build a Python Microservice Without Losing a Job