Please enable JavaScript.
Coggle requires JavaScript to display documents.
Scott's Microsite Movement (What do we need to do to make this happen?…
Scott's Microsite Movement
What is it?
Extracts the logic behind the ConfigurablePageController in the REI monolith to a microsite
It will utilize the ComponentsLibrary to render templates/pages
Why is this created?
This will extract logic out of the monolith!
This will convert the rendering logic to a crampon microsite
Benefits to this?
Site Production and SEO team can utilize the ComponentLibrary features
it will be a crampon application, which means that it can ingest libraries easier than the monolith
We're taking out an old implementation of the rendering logic
This will stop our work into getting the Components Library into the Monolith
What do we need to do to make this happen?
Get the components library into the components microsite.
This means that I have to update the caching in the library
I have a PR on this. I should check it out and submit PR
Move configurablepagecontroller into Crampon-microsite
update configurable page controller to use the components library
Move all the new beans in the Monolith to the library
We need to confirm which beans/methods to move to the library
I have a branch on this in the Library. Check it out and submit PR
This still might require us to work with the teams that knows some of the Bean's services to convert them to WebService methods
We started to reach out to Product for help, they said yes. We need to follow up and give them a deadline
I need to capture this shit in JIRA/Confluence
Once microsite is ready for PROD, then we will point traffic to the microsite instead of the Monolith?
How do we do this?
Code changes in the Monolith and/or shortcut tool update??
Shadow Queries
percentage of traffic still happens but it goes to both old and new
Having data to compare
What's the plans for the dead code in the Monolith?
Should it stay there in case the microsite doesn't do well initially?
Yes, at least initially. So we can flip the bit in case something goes wrong.
or NO. cause if something goes wrong then we can revert to a previous build.
What else do we need to do to the microsite in order for this to be ready for primetime?
Questions/Unknowns
How are we going to test this Visually?
Sit with Andreas to talk about the search caching situation
Cache 30 seconds
Find the story that explains the product and event beans and give it to Josephine