Decoupling the components can be a long and difficult journey. Start by identifying pieces that can be spilt out as services one at a time. Do not pick the easiest pieces but rather the pieces most in need of the benefits of SOA: flexibility, ease of upgrade and replacement, and so on.
Interesting. We did it this way and learned a lot of lessons slowly rather than quickly. Seems your first should perhaps be small, then jump straight to the most in need of isolation before going back to medium fruit?
Also, bug: "spilt" -> "split"
Small, easy show little value. Big and easy could show some value, but I find it similar to refactoring code because I don't like how the last per…