A Kafka-like queue on MySQL
Everybody knows you should not build a message queue on a database. I just did, and I think it was the right call.
Everybody knows you should not build a message queue on a database. I just did, and I think it was the right call.
When core data changes, something else has to happen. A cache entry must go, a search index must be updated, and an audit log wants to know what the value was before. I had one mechanism for all three in my previous job, and missed it in the new one. So I built it again from scratch.
Everyone is moving from XML to JSON. I just wrote a tool that goes the other way.
EclipseLink needs to change your entity classes to do lazy loading and change tracking properly. It can do that when the application starts. That sounds convenient. It has been a pain in the neck on every server I have set it up on.