redesigning a system

[icy leaf]

you have an existing system that you want to redesign because it's using an outdated framework/library that is no longer supported and it is getting difficult to manage. how would you go about it?

• do you keep ALL existing features? you discover some features aren't necessary or the way certain features works doesn't really make sense anymore and you want to refactor it
• do you create a brand new project so that way you can start fresh and keep running the existing app while you work on the new one?
• should you port pieces of the current application and roll them out instead of waiting for the entire new redesigned application to be completed that way you have some improvement?

[brave ridge]

<@&987246841693360200> please have a look, thanks.

[dusk hearth]

I first analyze the situation to determine whether it's feasible to modernize the application itself, or a rewrite is more opportune. In case of the latter, I like the strangler pattern if feasible.

[icy leaf]

ty didn't know of that pattern before. it seems useful as the migration is happening, but i think i'd want to remove the facade after the migration is complete obv giving clients time to update their code

i don't think i's feasible to modernize the application itself. i have microservices that are no longer necessary or have become a pain to manage and we want to consolidate things. (still tbd)

[oblique dagger]

You need to evaluate that want

[patent rover]

Modularization would be a good place to start, I think...
I mean, migrate pieces of the system and get them out to the users.

[icy leaf]

i am looking to migrate/rewrite my system so it's a modular monolith

what you said is what im thinking about. see my 3rd point

should you port pieces of the current application and roll them out instead of waiting for the entire new redesigned application to be completed that way you have some improvement?