tag:blogger.com,1999:blog-8655567.post114994873726850876..comments2023-10-30T01:48:47.905-07:00Comments on Panic From Fuzzy: EDA Lessons Learned - Batch vs EDAfuzzyhttp://www.blogger.com/profile/04442788840388847156noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-8655567.post-1149989617185667292006-06-10T18:33:00.000-07:002006-06-10T18:33:00.000-07:00We have a VSE mainframe among other things. Is tha...We have a VSE mainframe among other things. Is that old school enough for you ?<BR/><BR/>;)<BR/><BR/>I like your analogy - I'm going to have to use that with some of our mainframers.<BR/><BR/>Thanks Jack!fuzzyhttps://www.blogger.com/profile/04442788840388847156noreply@blogger.comtag:blogger.com,1999:blog-8655567.post-1149966363256567852006-06-10T12:06:00.000-07:002006-06-10T12:06:00.000-07:00Hi mike, previous message was mine...Hi mike, previous message was mine...Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8655567.post-1149966262929907592006-06-10T12:04:00.000-07:002006-06-10T12:04:00.000-07:00I have my roots in the old IBM370 JCL. What I like...I have my roots in the old IBM370 JCL. What I like about EDA is that designing an EDA is very similar to designing batch job flows. Where you write a record to a file, you publish an event. Reading from a batch file is consuming from a topic. Where you read multiple files in balance, you come to complex event processing. Batch programs are decoupled. Programs write records and others read records, without any knowledge of each other's existence.<BR/><BR/>Simply said: Just take out the read/write-to-end-of-file loop from a batch program and the program is modernized to play its real-time role in an EDA. <BR/><BR/>Another way is to slice up batch files to messages and to queue up messages to batch-files; both at the perimeter of the ESB. <BR/><BR/>This is the way I explain the EDA-mindset to our analysts and programmers. And it works... (as far is they are old enough to know anything about batch programming ;-)).Anonymousnoreply@blogger.com