This content has been marked as final. Show 3 replies
Please clarify. Is this a one-time data migration project? If so I can't imagine why you are looking at any solution beyond Java plus JDBC. You don't need any of that other stuff.
No dear. This is not a one time data migration. it should configured with spring schedulers to continusly
Now clarify as to whether this is copying from db2 to mysql only or if you have to synchronize the two, i.e if you have to copy from mysql to db2 as well.
you have other functional questions to ask as well like
Can there be duplicates and are you supposed to detect them?
Are you allowed to extend the original tables with extra columns to mark them as processed?
Personally I don't see the point of JMS here (it's best for integration between two Java systems and all you're doing here is DB work). I would also not use an application server for batch processing involving huge data, especially since you are already using spring which offers spring batch. Maybe with the container you'll gain with some transactional aspects if you can XA and only commit if you have both written to target and updated source as processed.