@LeledumboThe purpose of tutorial is to focus, modularization may hinder that purpose. After all, if you already understand modularization, the modular design would be up to you. Some people use a single unit that uses every other units providing the routes then register it there at initialization section, this helps maintenance by centralizing route registration in one place. Others instead, put the registration in each respective unit, making route registration modular and therefore, also helps maintenance. Now which one do you think is better and I should make a tutorial for? If you have an exact answer, you might need to learn modularization again, as there's no definitive better of the two, each has its own pros and cons.
Can you add another example that separates procedures of route and route2 of webserver example into another unit in your tutorial? I know how to do now, but in the beginning I had some difficulty in figuring out the working mechanism of new routing system. And separating units has advantages in later maintenance, especially when there are many procedures, and when we try to access a datamodule that accesses database.
Of course this is not a request... just my suggestion. Acceptance is up to you.
But with some trial and errors, I found that I only have to redefine procedure headers, and old and new routings can co-exist.Assuming HelloRequest calls Hello (this is the flow I suggest, not the other way around), yes both can coexist, but one is mutually exclusive from another, as there's only one can be active at any given time through that LegacyRouting switch. It could be put in the tips and tricks section.
Short mentions about these features would lessen the burden of trial and errors from developers, I think.