http://www.marketingpilgrim.com/2009/06/the-reality-of-real-time-hits-real-hard.html Internet Marketing News Fri, 10 Feb 2012 16:14:39 +0000 hourly 1 http://wordpress.org/?v=3.3.1 http://www.marketingpilgrim.com/2009/06/the-reality-of-real-time-hits-real-hard.html/comment-page-1#comment-76905 Wayne Sutton ’s lifestream activity for June 26th | WayneSutton.me Sat, 27 Jun 2009 09:32:30 +0000 http://www.marketingpilgrim.com/?p=11286#comment-76905 [...] The Reality of Real Time Hits Real Hard — 4:31pm via Google [...] [...] The Reality of Real Time Hits Real Hard — 4:31pm via Google [...]

]]> http://www.marketingpilgrim.com/2009/06/the-reality-of-real-time-hits-real-hard.html/comment-page-1#comment-76875 ryantxr Sat, 27 Jun 2009 05:22:53 +0000 http://www.marketingpilgrim.com/?p=11286#comment-76875 One of the best articles I've see recently. I do agree that people are fast becoming accustomed to getting information immediately. As it should be. Application and system developers who think in terms of batch are the ones who will be in trouble. I recall several development situations where we were integrating several different platforms, the first discussion was about what files each team would throw to the other. "Why wait a whole day?" I asked. Why not just connect when you want the information and just get that one small piece? If there's a problem, then it's only that one small piece that needs attention instead of a whole file load of information. My idea ended up winning and I forced the mainframe team to process XML messages on the fly. Turned out to be a good move. The process hardly needed any attention. Come to think of it. I'm inventing the batch soda machine. Put in a dollar and come back in an hour when I process your batch. One of the best articles I’ve see recently. I do agree that people are fast becoming accustomed to getting information immediately. As it should be. Application and system developers who think in terms of batch are the ones who will be in trouble. I recall several development situations where we were integrating several different platforms, the first discussion was about what files each team would throw to the other. “Why wait a whole day?” I asked. Why not just connect when you want the information and just get that one small piece? If there’s a problem, then it’s only that one small piece that needs attention instead of a whole file load of information. My idea ended up winning and I forced the mainframe team to process XML messages on the fly. Turned out to be a good move. The process hardly needed any attention.
Come to think of it. I’m inventing the batch soda machine. Put in a dollar and come back in an hour when I process your batch.

]]>