4 ms·
The transport technologies already exist; Camel unifies them under a single API. What you get in return is precisely not having to manage all of them in your ow
by davelnewton 10y ago
The transport technologies already exist; Camel unifies them under a single API. What you get in return is precisely not having to manage all of them in your own code.
Simplistic problems don't demand complex solutions. Complex problems do. If you're not doing anything complex enough to require a complex solution, then of course you wouldn't need something like Camel or any other ESB-like solution.
¯\(°_o)/¯
- unclebucknasty 10y agoSure. I'm saying that Camel doesn't seem to provide what's advertised for those complex cases. Instead, it adds a layer of obfuscation and more constructs to manage to what could otherwise be clean code. I think we just disagree on that point, as I apparently do with everyone regarding Camel. But, I don't fret. I also thought J2EE was completely nuts when everyone still believed it was the new sliced bread. :)