At this point in the history of programming, everyone pretty much knows what microservices are and everybody is more than acquainted with the legacy code – and often monolithic code – that has been created over decades by countless programmers who have evolved corporate applications to fit new conditions and new demands.
It is often called spaghetti code, and for good reason. The code is often a tangled mess of business logic and data – presumably the data is the meatballs and the user interface is the sauce in this metaphor. (It is important to not take a metaphor too literally, of course.) While ARCAD Observer can help IBM i developers figure out the architecture of these applications and ARCAD Transformer RPG can help convert older RPG applications to modern free form RPG – in this metaphor, these help you figure out what you are going to eat of the spaghetti code. But a new tool called ARCAD Transformer Microservices, ARCAD is now helping developers figure out where to bite first as they try to eat that plate of spaghetti code to change it into modern, modular microservices, one piece of spaghetti at a time without risk of splashing tomato sauce or meatballs on users’ white shirts.