Timeline for DAO design for writing big XML file on database
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 3, 2016 at 17:24 | comment | added | Matthew Mark Miller | Yeah I wouldn't handroll any of that (except maybe "supportability" -- I found explaining SB's generic task execution model to operators to be more difficult than a task specific audit model). But there are lots of ways to get those behaviors when needed these days -- a good actor framework is my preference. | |
| Jan 3, 2016 at 14:01 | comment | added | maple_shaft♦ | This is a very well thought out answer. I still think Spring Batch framework is the best approach considering things like load balancing, partitioning job execution, supportability in production and exception management, but this is the best approach over all with the given constraints. | |
| Jan 3, 2016 at 12:30 | comment | added | amekki | I would like to thank your for your post. It seems very helpful for me. | |
| Jan 3, 2016 at 8:15 | history | answered | Matthew Mark Miller | CC BY-SA 3.0 |