Spike: Formalize proposal to improve Plan management in CustomersDot
Problem
As stated in the description of Improve Plan / SKU management in CustomersDot (&6579 - closed), the product catalog lives in Zuora. It goes against our stated goal of Zuora as the SSoT if CustomersDot code has much of the product catalog knowledge baked into the code. We want to improve the architecture and maintainability of the Plan
model.
Over a year ago, we started to identify a proposal for improved Plan mangement in CDot with the design epic, Discovery: Improved plan configuration/manageme... (&7750 - closed). However, given some time has passed since then, let's re-evaluate if this is still the best course of action.
Proposal
Let's define a proposal, perhaps an architecture blueprint, to improve Plan management in CDot. We could look at Discovery: Improved plan configuration/manageme... (&7750 - closed) and its issues for reference but also keep an open mind for any new ideas as well.
One idea to explore: With the Zuora integration gem, IronBank
, CDot already has a cache of the Product catalog (Zuora::Product
, Zuora::ProductRatePlan
, Zuora::ProductRatePlanCharge
, Zuora::ProductRatePlanChargeTier
). If we can move some of the classifications that are hard-coded in CDot into Zuora, then we might be able leverage the cached catalog more and perhaps get away from the current Product
and Plan
models.
Result
A defined proposal or blueprint for better Product and Plan management in CDot. A well-defined epic with actionable issues.