As I delved deeper into the discussions over the last few weeks, the challenges became a lot clearer and increasingly apparent. The tightly coupled modules and the massive Oracle database continued to be the focal points of our discussions. With only one developer possessing limited knowledge of the application, we found ourselves navigating through issues such as getting time from the developer, unknown assumptions, and several undocumented dependencies.
The initial domain identification process is still ongoing and getting time-consuming. Engaging with stakeholders and domain experts is not as planned as there are none :-(. Also discovered that what appeared to be distinct domains often had hidden interdependencies, further complicating our decomposition strategy.
The budget constraints also loom large as we progress. Every potential solution had to be weighed against its cost implications, forcing us to think creatively about resource allocation. The initial plan of migrating to the cloud is now squashed.
One promising approach that I think could be a good fit is the strangler fig pattern. This strategy will hopefully allow for incremental modernization by gradually replacing specific functionalities of the monolith with microservices using the same technology. We identified a few non-critical modules that could serve as our initial targets to not risk core business operations.
As we move forward, the next crucial step is to create a business capability matrix and a detailed modernization roadmap. This roadmap will prioritize modules for decomposition based on their business value, technical complexity, and potential for immediate impact.
The next steps seem to be a long process, but I am getting much more optimistic than before. Hopefully, the next time I write I will have the approach and roadmap finalized.
To be continued...
No comments:
Post a Comment