Determining if the license seat links architecture could be changed
Recently we discussed the growth of License seat links in the Architecture Review: Fulfillment Platform Meeting
Recording: https://www.youtube.com/watch?v=v99sNJiVkW4
Presentation: LicenseSeatLink growth
Problem
We use LicenseSeatLinks
to record seat usage and track other changes for self-managed
orders
- An Order has many
LicenseSeatLinks
- To track changes for
LicenseSeatLinks
We introduced LicenseSeatLinkVersion
While self-managed orders database usage ~= 5.95 MB
Looking at the total size of the CustomersDot
database, compared to those tables
Total database storage = 19.34 GB
license_seat_link_versions
are ~ 2.96 GB
license_seat_links
are ~ 1.8 GB
( 2.98 + 1.8 ) = 4.78 GB
~= 24.82 %
of total database storage!
This seems to be a lot of LicenseSeatLinks
and database usage!
Proposal
-
We need to investigate why we have
license_seat_links
in the first place.- Should it be a 1:m relationship?
- Can we break the
license_seat_links
into different tables?
-
We need to investigate why we have
license_seat_link_versions
in the first place.- Which kind of changes we are tracking?
- Can we break have a different solution?
Result
TDB
Next steps (if any)
TDB
How will we measure success?
TDB