In modernization, one size does not fit all
Everything we have talked about so far has been focused on re-architecting your monolithic workloads. You might think that this implies that you are rewriting most, if not all, of the workloads, but it does not have to always be that way. It’s time for a quick recap to make sure we are clear on semantics. Here are a couple of terms to review:
- Rehost: Typically, this refers to taking the existing code base from the monolith and recompiling it for the x86 platform so that it can run in Azure
- Refactor: This is very similar to rehost but implies that the language has changed, usually from COBOL (or some other legacy language) to Java or C#
Remember earlier in this chapter in the Understanding how we got here – the evolution of application development section, how we talked about how, as monoliths evolved, they started employing modular programming into their architectures? This is good news if we want to reuse...