Re: [DISCUSS] Chronicle Queue's development model and a hypothetical replacement of the library

2024-09-17 Thread Štefan Miklošovič
to Benedict: well ... I was not around when the decision about the usage of Chronicle Queues was made. I think that at that time it was the most obvious candidate without reinventing the wheel given the features and capabilities it had so taking something off the shelf was a natural conclusion. J

Re: [DISCUSS] Chronicle Queue's development model and a hypothetical replacement of the library

2024-09-17 Thread Benedict
My point is only that AFAICT we use it for something incredibly basic that we do all the time elsewhere without it.I’m not proposing we remove it, I don’t have a position on that. But if we don’t _trust_ ourselves to replace it we should get out of the database game.The fact it would break compatib

Re: [DISCUSS] Chronicle Queue's development model and a hypothetical replacement of the library

2024-09-17 Thread Štefan Miklošovič
There are configuration properties related to controlling what that bin log does in runtime so if we completely changed the vehicle it operates on then the only thing which would stay in common is the name of the command and the logical operation it does (enable / disable, get the config if there i

Re: [DISCUSS] Chronicle Queue's development model and a hypothetical replacement of the library

2024-09-17 Thread Benedict
All of these options are managed by us, the only property that is passed through to chronicle is the “RollCycle” that we can trivially replicate, or that we could simply deprecate.On 17 Sep 2024, at 09:57, Štefan Miklošovič wrote:There are configuration properties related to controlling what that