Please enable JavaScript.
Coggle requires JavaScript to display documents.
Implement Components Library in the Monolith (Any possible roadblocks?…
Implement Components Library in the Monolith
What does this mean?
Replace existing rendering logic with the library
What does this include?
Rendering Factory
Implemented Beans
The library will render components rather than the original
Any possible roadblocks? Issues to address?
There's duplicate bean implementations in both the monolith and the Library
What are the dupes?
ComponentUtilApi
Duplicate method signatures but different implementations, maybe slightly but I cannot tell upon initial glance
ContentApi
Monolith has added getMap(). Also,
Mono uses CmsWebService (internal) instead of ContentWebService
NavigationApi
Monolith uses NavigationWebServiceClientBreaker instead of NavigationWebService
Monolith has added get() method
AssetApi
Same logic, except that Mono uses CmsWebService (internal) instead of ContentWebService
Are there any dupes that are vastly different in logic?
How to handle this?
There's annotated beans that exist in the monolith that aren't int the library
What are all the beans?
BrandLandingApi
ExpertAdviceApi
ProductApi
Does NOT use hystrix
EventRegApi
InspriationalContentApi
How to handle this?
There's no way to know which beans are being used in widgets
How to handle this?
Update CMS to provide a search endpoint that can help us find all widgets. Customized by filter
This is a maybe. Most of the beans have a
Timed
annotation on their methods. Maybe I can use that somewhere... grafana?
The monolith uses HystrixCircuitBreaker for a lot of the beans