Mach-II & Reactor

No, I've not started using these together, but I have delved into quite a few architectures / time saving ideas reacently, and these two have particularly stuck out at me as very useful systems.

Mach-II allows event creation and event chaining, as well as handling the creation of beans (a concept that I'm only now becoming familiar with... thanks BS CS degree).

Fusebox seemed like about the same thing as Mach-II, but I was turned off by a couple of things... the terminology was very slanted, and while I'm sure "circuits" and "fuses" make a lot of sense to some people, I'm a programmer not an EE guy. Secondly, this is still very much a procedural setup... and its not to say that that is bad, but I'm more interested in OO design.

I looked into Coldspring, but to be honest, I'm not seeing the huge advantage right now... I follow that it allows you a more loosely coupled design, but I'm not seeing any time saving benifits of the setup. Secondly, I'm not 100% following the benefits of the bean factory and everything else... I will have to do more research.

Model Glue confuses me... it seems like exactly the same setup as Mach-II, only they call events events... wait I mean they call event-handlers event-handlers... wait I mean they call events viewStates. Ok, finally something different. Perhaps MG works better then Mach-II? I don't know.

As for Reactor, its not so much of a Framework at all, as a way to handle datamanipulation without creating hundreds of DAOs by hand. I'm going to investigate the performance costs of this method, but like with Mach-II, they seem to be low once you start getting into production mode.

Jon Hartmann, July 2011

I'm Jon Hartmann and I'm a Javascript fanatic, UX/UI evangelist and former ColdFusion master. I blog about mysterious error messages, user interface design questions, and all things baffling and irksome about programming for the web.

Learn more about me.

Post a job. Find one.

Interested in becoming a sponsor? Contact me.