Open jennb33 opened 4 months ago
@LindseySaari we need to communicate this to Jeff K and see what other ideas need to be included in this Epic and that he is aligned with it. Jeff should also perhaps synch with Bill to make sure we are breaking the right pieces into Microservices. Aparna to make sure that Bill and Jeff are in alignment.
Product Outline
Link
Summary
This epic captures our strategic shift from a Rails monolithic framework to a hybrid microservices architecture. This transformation aims to streamline development autonomy across VFS (Veteran-Facing Services) teams and facilitate the isolation of distinct application functionalities. Automation will be pivotal to the seamless integration and operation of monolithic and microservices components within our ecosystem.
Objectives
Key Benefits
Enhanced Scalability
Leveraging microservices enables targeted scaling of application components, isolation and optimizing both resource utilization and operational costs.
Accelerated Development Velocity
The independence afforded by microservices architecture allows teams to rapidly develop, test, and deploy, significantly speeding up release cycles.
Technological Flexibility
Microservices architecture facilitates the exploration and adoption of new technologies within isolated components, without necessitating broad architectural overhauls.
Increased System Resilience
Isolating services limits the scope of potential failures, thereby improving the overall resilience and reliability of the system.
Milestones
Assessment and Strategy Formulation
Infrastructure and Tooling Configuration
Pilot Microservice Implementation
Systematic Component Migration
Automation and CI/CD Optimization
Knowledge Sharing and Documentation
Performance Evaluation and Refinement
Challenges and Strategic Considerations
High Level User Story/ies
As a developer, I need to transition our application from a monolithic architecture to a hybrid microservices architecture so I can enable individual teams to deploy updates faster, reduce overall system downtime, and improve scalability.
Hypothesis or Bet
If we restructure our application into a hybrid microservices architecture then we expect to achieve faster feature deployment times, product/application isolation, lower the risk of system-wide failures during updates, and enhance our application's scalability to handle growing user demand.
OKR
O2. Our platforms are the best way to deliver products at VA OKR 1: Our platforms hit the "elite" level (as defined by DORA) on Deployment Frequency, Lead Time for Changes, Change Failure Rate, and Time to Restore Service.
Definition of done
Definition of Done
Take into consideration Accessibility/QA needs as well as Product, Technical, and Design requirements.