Initiative: Rebuild the Analyst Database
Created Date | Mar 30, 2023 |
---|---|
Target PI | Initiative - spans PI 2 through 6 |
Target Release | Oct 1, 2023 |
Jira Epic | |
Document Status | Hold Draft Review Committed At RISK |
Epic Owner | @John Hunt @Ben Bradley |
Stakeholder | |
Engineering Team(s) Involved | Analyst |
PART 1
Technical Problem
This is a forced change
to upgrade from MySQL 7 before it stops being supported in October 2023.
Value to Customers & Users
For Customers, our solution adds:
the technical ability to put an Analyst instance in the closest AWS datacenter to large customer centers
Value to Lightcast
For Lightcast it provides:
security
long-term database support
better disaster recovery
Target User Role/Client/Client Category
Who are we building this for?
Delivery Mechanism
The Analyst Platform
Success Criteria & Metrics
Analyst is running on the new database before MySQL 7 support is shut down
Aspects that are out of scope (of this phase)
What is explicitly not a part of this epic? List things that have been discussed but will not be included. Things you imagine in a phase 2, etc.
PART 2
Estimated Costs
Direct Financial Costs
Are there direct costs that this feature entails? Dataset acquisition, server purchasing, software licenses, etc.?
Team Effort
Each team involved should give a general t-shirt size estimate of their work involved. As the epic proceeds, they can add a link to the Jira epic/issue associated with their portion of this work.
Team | Effort Estimate (T-shirt sizes) | Jira Link |
---|---|---|
|
|
|