How cool if we made plans pages CAAS clients?

[npeltier]

we are exploring in milo migration of plans page the possibility to use caas for managing card collections (catalog, different tabs, product cart, ...), we'd plugged some specific tools in (only thinking around cart right now).
Authoring is not our main fear here, more front end complexity & performance.

Any first thoughts / ideas ?

[auniverseaway]

I personally think CaaS is already trying to do too much, but I would defer to @jedjedjedM and @sanrai.

[npeltier]

well, for me Caas is supposed to be our card system, and mentionned pages are mostly cards. Making it ready for our use case (features + perf) is something we'll have to look into sooner or later (cc @honstar i've been discussing this with for the last 5 years :p)

[honstar]

I agree that CaaS should at least consider the use-case of having commerce enabled cards, especially in light of its use-anywhere nature. I know that the javelin team is already looking into this by building a PoC to serve cards with prices and checkout links.

It is tbd if cards with commerce data should be served by CaaS in a baking or frying manner. With the former, all processing would sit on the CaaS (server) side whereas the latter would be a mix of CaaS serving commerce cards and relying on the client to fetch prices and generate checkout links.

[npeltier]

we are considering as orthogonal concepts the "authoring" & serving of card stream payload that milo caas offers nice opportunity on, and rendering of it which could be possible with a few changes:

• we'd need FE caas libraries to modularized (so we only get what we use),
• we'd need to be able to plug some other components to collections there
  cc @jedjedjedM @sanrai

[jedjedjedM]

I do think it is worthwhile to do an evaluation. CaaS is not up to milo performance standard currently, but Sanjay is actively pursuing many parallel paths to get the lighthouse score in the green. Additionally, we (Carlos) also have a commerce card use-case that we are building out in Q3 which will be used for black friday. Based upon the success (or failure) of these initiatives, we should have some learnings at the end of the quarter.

Let me know if there is anything the team can do to help with gap analysis.