Comments (2)
  • Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

1 frodenas commented Permalink

Hi Martin, <div>&nbsp;</div> Batch architectures is a really nice topic to discuss, as there's a lot of science behind big batch workloads. Unfortunately, you won't find so many posts, books, ... about this kind of architectures, and it's a shame because as you stated, "many installations would benefit from drawing up a Batch Architecture". <div>&nbsp;</div> I concur with your list of containing elements. A well updated app's inventory (with attributes as critical, SLA's, windows, responsibilities) is basic for MTTR, as some failures need urgent diagnostics or it's recovery depends on an specific dev team. Interfaces is also important, as you can draw dependencies between jobs. <div>&nbsp;</div> There are also some other important topics to cover: Schedulers, # dedicated init class, tiered storage, subsystem availability, ftp, WL classes, ... but the list is so long to write it on a comment :) <div>&nbsp;</div> In my current company we've a well established batch architecture, and we enforce it via custom dev and ops tools. Just 3 facts about our installation: <br /> - We tend to speak about biz objectives, not jobs. A biz objective can be composed by several jobs of different apps. <br /> - We've a team whose responsibility is to analyze Batch performance. They analyze the #toptem batch jobs and they propose improvements. During the last 1 year, we reduced the peak batch workload by several K MIPS. <br /> - We're now defining a batch architecture for our Java app's (sorry, x86 arch not running on a blade :) ). We use the mainframe architecture as an example (to copy something that is working extremely well) <div>&nbsp;</div> Waiting for your next post!

2 MartinPacker commented Permalink

Ferdy, thanks for this contribution. You raise some very good points. Clearly my list and examples weren't exhaustive. And thanks for sharing what you do. I agree that a business focus is important. Maybe the ability to have that is another key benefit: I suspect a lot of customers are some way from being able to do that - not to insult ANYONE. :-)