Spring boot Axon Postgres

When implementing event sourcing with spring boot using axon, we all first notice the every second token entry update. This is a normal behavior and was discussed under other open topics.

But did someone notice that this behavior will significantly impact your Postgres database’s Write-Ahead Log (WAL) size and performance?

What should be done in such cases?

Thanks for any help in advance.

Hi Majd, if you are using Axon Server, you can consider and test a feature that we will release quite soon: persistent stream. With persistent stream you avoid need for token store and frequent token entry update, and Axon Server keeps the track how many events your client consumed and how many remains to be sent.

Hi Stefan, sure I will check this new feature once it is released. Thank you.