How to deal with cyclic dependencies?

[shwetakawale]

There could be situation like
Module A (Order) depends on Module B (Inventory):
Whenever a new order is placed, Module A needs to call Module B to check if the required inventory is available.
Module B (Inventory) depends on Module A (Order):
Module B needs to be notified when an order is placed, updated, or canceled so it can adjust inventory levels accordingly.

but in spring modulith it leads to cyclic dependency, there could many such usecases, is there any way to solve this @odrotbohm

[aahlenst]

High coupling of two modules either indicates that they should be a single module or that design needs to be improved. To break the cycles, you have two options: Introduce a third module that depends on the first two or move classes around. In this case, you could remove the dependency from Order on Inventory. If Inventory is notified of new orders anyway, Inventory can call Order directly to cancel the order if the required inventory is unavailable instead of Order asking Inventory whether there is enough stock.

[odrotbohm]

Sometimes you can invert the dependency by introducing an interface on the one side that's implemented by the other. So the former requirement might be inverted by introducing a StockAware in the order module that the inventory implements.