Very good article! I also implement hexagonal architectures using maven modules and I wondered where to put ports. Currently I have core module (instead of model), where I put domain and interfaces. That way my adapters do not have to have dependency on the application module. Application module from logical point of view looks like a better place for ports and with ArchUnit we can guard ourselves against leaking too much. I will give it a try.

Very good article! I also implement hexagonal architectures using maven modules and I wondered where to put ports. Currently I have core module (instead of model), where I put domain and interfaces. That way my adapters do not have to have dependency on the application module. Application module from logical point of view looks like a better place for ports and with ArchUnit we can guard ourselves against leaking too much. I will give it a try.

Very good article! I also implement hexagonal architectures using maven modules and I wondered where to put ports. Currently I have core module (instead of model), where I put domain and interfaces. That way my adapters do not have to have dependency on the application module. Application module from logical point of view looks like a better place for ports and with ArchUnit we can guard ourselves against leaking too much. I will give it a try.

Very good article! I also implement hexagonal architectures using maven modules and I wondered where to put ports. Currently I have core module (instead of model), where I put domain and interfaces. That way my adapters do not have to have dependency on the application module. Application module from logical point of view looks like a better place for ports and with ArchUnit we can guard ourselves against leaking too much. I will give it a try.

Very good article! I also implement hexagonal architectures using maven modules and I wondered where to put ports. Currently I have core module (instead of model), where I put domain and interfaces. That way my adapters do not have to have dependency on the application module. Application module from logical point of view looks like a better place for ports and with ArchUnit we can guard ourselves against leaking too much. I will give it a try.

Very good article! I also implement hexagonal architectures using maven modules and I wondered where to put ports. Currently I have core module (instead of model), where I put domain and interfaces. That way my adapters do not have to have dependency on the application module. Application module from logical point of view looks like a better place for ports and with ArchUnit we can guard ourselves against leaking too much. I will give it a try.

Very good article! I also implement hexagonal architectures using maven modules and I wondered where to put ports. Currently I have core module (instead of model), where I put domain and interfaces. That way my adapters do not have to have dependency on the application module. Application module from logical point of view looks like a better place for ports and with ArchUnit we can guard ourselves against leaking too much. I will give it a try.

Very good article! I also implement hexagonal architectures using maven modules and I wondered where to put ports. Currently I have core module (instead of model), where I put domain and interfaces. That way my adapters do not have to have dependency on the application module. Application module from logical point of view looks like a better place for ports and with ArchUnit we can guard ourselves against leaking too much. I will give it a try.

Very good article! I also implement hexagonal architectures using maven modules and I wondered where to put ports. Currently I have core module (instead of model), where I put domain and interfaces. That way my adapters do not have to have dependency on the application module. Application module from logical point of view looks like a better place for ports and with ArchUnit we can guard ourselves against leaking too much. I will give it a try.

Very good article! I also implement hexagonal architectures using maven modules and I wondered where to put ports. Currently I have core module (instead of model), where I put domain and interfaces. That way my adapters do not have to have dependency on the application module. Application module from logical point of view looks like a better place for ports and with ArchUnit we can guard ourselves against leaking too much. I will give it a try.