I'm planning out a microservice adoption for a rather big monolith. The current plan is to create new features using microservices and constantly extracting features from the monolith into services.
During that process is it problematic to let microservices talk to the old monolith?
For example, A new Product is developed but the
Cart Service is still located inside the monolith, so the new microservice has to call the monolith in order to add items and remove them.
Does anybody have experience with this kind of problems? Is this generally considered a bad practice and why? Is it better to just go through the pain and only migrate services that can run independently of the monolith?
Note: I'm generally aware that to much "chatter" between the services is considered bad, but in some cases, it's still required.