Do you have an example of the sort of transformations you're after? With names changed to protect the innocent, obviously.
I'm sure you could then elicit a few snippets of code from this list to demonstrate the different approaches, which should help you decide. On 26 January 2012 21:11, Rakesh <[email protected]> wrote: > well we may want to take the data and also send it to a data warehouse > for reporting at some point.... > > On 26 January 2012 21:07, Wayne Fay <[email protected]> wrote: > >> its ongoing for sure. The stack you mention seems a bit heavy weight... > > > > These ESB platforms generally only load what you need (ala OSGI) so > > while they have a long list of supported components, you will rarely > > load more than what you're actually using for your specific > > implementation. I can't make specific claims about performance for > > your situation but we have been happy with our ESB experiences. > > > > And I did say... > >>> important part (business logic/transformation) in the middle. This may > >>> also be total overkill depending on the specifics of your project but > >>> something to consider. > > > > If this is a single app to move data from one place to another, an ESB > > is probably overkill. If you anticipate a future need to pipe the same > > data (via another transformer or the same one etc) to another > > destination (endpoint), or do some other analysis of the data, you may > > find this to be a useful foundation block that you can build on (as we > > have). > > > > Wayne > > > -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
