Looks like I need to setup a new Java environment for some interfaces we need to build.
Say our system is X and we need to interfaces to systems A, B and C. Then we will be writing interfaces X-A, X-B, X-C. Our system has a bus within it, so the publishing on our side will be to the bus and the interface processes will be taking from the bus and mapping to the destination system.
Its for a vendor based system - so most of the core code we can't touch.
Currently thinking we will have several processes, one per interface we need to do.
The question is how to structure things.
Several of the APIs we need to work with are Java based.
We could go EJB, but prefer to keep it simple, one process per interface, so that we can restart them individually.
Similarly SOA seems overkill, although I am probably mixing my thoughts about implementations of it compared to the concepts behind it...
Currently thinking that something Spring based is the way to go. In true, "leverage a new tech if possible"-style, I am thinking maybe we can shoe horn some jruby into this, perhaps to make the APIs more readable, perhaps event-machine-like and to make the interface code more business-friendly, perhaps even storing the mapping code in the DB, as ruby snippets that get mixed in... but thats an aside...
So, any comments/thoughts on the Spring approach - anything more up-to-date/relevant these days.
EDIT: Looking a JRuby further, I am tempted to write it fully in JRuby... in which case do we need any frameworks at all, perhaps some gems to make things clearer...
Thanks in advance, Chris