Thanks for the added background there.
The two sentence request you dropped was insufficient for me to deduce your situation or suggestion.
When it comes to the SQLErrorCodesResolver your statement seems fair.
Added though, adjusting and configuring a different/updated SQLErrorCodesResolver should be doable through the PersistenceExceptionResolver.
If you see personal value in introducing this, you are more then free to contribute to Axon Framework; that would be beneficial for you, us and the entire community and as such would be very much appreciated.
Just pointing it out will however not get it resolved right away, so in the end we might just need some help from contributors on this part.
To file a feature request, you browse to the framework’s GitHub page.
Then to your second point, Kafka.
It makes total sense you are not proceeding towards Axon 4 yet given your usages of the Kafka Extension.
I do want to point out that the state of the Kafka Extension is similar to it’s state in Axon 3.x.
We’ve just made it more explicit that it’s a work in progress by having it not yet fully released.
We have plans to proceed working on it by the way, I can however not give you a time frame at the moment.
Another approach to dispatching events between microservices, as pointed out earlier, is Axon Server which mind you, is free to use taken the SE option.
Other than that, you can leverage the AMQP extension, or go very basic and share the Event Store datasource between your services.
Hope this clarifies your situation Prasanna.