Is this production ready?

[Kjarrigan]

Hi Lars,

thanks that you share the discussed eventbased system. Have you gathered some production-experience already? Does it work more stable than the old-system?

[larskanis]

Hi Holger, thanks for asking - and sorry for my late answer!

I'm very satisfied with the current state of Eventbox. The code is pretty clean and well designed. Even with the very first iterations of Eventbox it proved to be more a reliable and more maintainable approach than the previous plain usage of threads and locks. This is mostly due to the separation of management logic from the actual work (the blocking operations) which is enforced by Eventbox.

Have you gathered some production-experience already?

Not yet. Although it's passing all tests already - even the load tests passed from the start - I didn't want to change this mission critical system before my vacation.

Does it work more stable than the old-system?

Regarding reliability of operation I'm pretty sure - that's what the tests already showed. The proof of running in production will follow in 3 weeks, when I'll back at work.

Regarding stability of the API I'm pretty sure, that it will change in some way or another in the future. I currently don't care about compatibility at all. But I don't expect fundamental changes any more. Most changes were mostly search-and-replace things.

Things I currently plan to change:

• the sanitation of arguments (the mutable_object method, maybe a way to pass unsafe objects)
• use of Eventbox in modules as mixin
• simple usable timer events as mixin

[Kjarrigan]

So a few months later - any news?

You have done and changed quite a bit.