Esfera Médica — Microservice Ecosystem Evolution
Returned as a freelancer to continue evolving and maintaining a 4-microservice ecosystem I had previously designed and implemented as an in-house architect.
Stack: PHP 8+, Laravel 9, Laravel Nova, Livewire 2, Vue.js 2, MySQL (multi-database), MeiliSearch, Pusher, Redis, Amazon S3, Docker
Challenge
Need for continuous ecosystem evolution maintaining architectural coherence, incorporating new clinical and financial modules without breaking existing contracts between microservices.
Technical Approach
Maintenance and evolution of the microservice ecosystem architecture. Design and integration of new modules respecting existing bounded contexts. Development of printed formats for medical records with reusable templates. Implementation of commission management module aligned to existing financial model.
Architecture Decisions
Evolution over reconstruction
Leveraged the existing ecosystem (4 microservices, Docker network, shared-core) instead of proposing redesign, prioritizing business operational stability and keeping service contracts intact.
Impact & Results
- Serving ~950 patients, supporting complete ecosystem daily operation
- Recurring generation of 500–600 monthly invoices across microservices
- Up to 70% reduction in administrative work time through digital clinical records
- Architectural continuity of the ecosystem without operational interruptions
Key Insights
Resuming a system you originally designed allows evaluating architectural decisions with temporal perspective. Clinical data modules require strict data contracts and regulatory compliance.