Migrating from Traditional to Reactive

Evaluate the architecture

You will not want to transfer problems to your new code, right? Yes, but you don’t need to fix all kind of errors in your system. Usually architectural problems are the most common to be solved. You need to evaluate if there are cyclical references or undue access between the layers of your application. You can use the Discovery tool to check the quality of your system and if the fixes worked properly.

Define development metrics

Long story short, in the beginning I thought that I could use the menu options as reference to generate metrics. It didn’t work well. The best alternative I found is the number of screens and I disregarded the number of web blocks because they are reused in other screens.

Average for estimation creation
Planning project — general view

Tips for development

Maybe you would like to see the differences between traditional web and reactive applications. I already wrote an article about this subject (it can be seen here) and, I added more tips here that can save you more time.

Conclusion

Migrating to reactive can be done in a strategic and purely programatic way. From the strategic perspective, it was presented a simple way to get a rule of thumb to grasp an estimative to your customer, for instance. From the development perspective, it is possible to learn based on previous experience on commercial projects. Both contributions can be used as foundation to increase the software development speed and quality. I hope you enjoyed this article and have a nice week.

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Luciano Schiavo

Luciano Schiavo

27 Followers

PMP Certified | Togaf 9 and Business Architecture Certified| LSS Black Belt | Solutions Architect |Productivity Improvement Researcher