It's all about chunking

It's all about chunking

Summary: Musing more about Tuesday's SOA Executive Forum, one thought seems to stick out. A number of speakers described service-oriented architecture as the process of breaking applications into bite-size chunks to be delivered when and where they are needed.

SHARE:
TOPICS: Tech Industry
1

Musing more about Tuesday's SOA Executive Forum, one thought seems to stick out. A number of speakers described service-oriented architecture as the process of breaking applications into bite-size chunks to be delivered when and where they are needed.

Henry Ford was a fan of "chunking" -- he broke automobile production down into chunks when he mastered the assembly line.  We saw the chunking of operational or office-based processes with the advent of the computer. When I became a director with the Administrative Management Society in the late 1980s and 1990s, the chunking of white-collar and administrative tasks into more standardized and automated tasks (word processing, reporting, database management) was sweeping through organizations. 

Tom Peters, co-author of In Search of Excellence, talked about chunking as a strategy for breaking up complex tasks and projects into manageable components. Now, we are talking about the chunking of software itself.   The question is -- and this was raised at Tuesday's sessions -- can we achieve simplicity by breaking down complex software operations into manageable, bite-size chunks? Or will things end up as brittle as the CORBA (Component Object Request Broker Architecture) efforts of the past decade? We'll see plenty of successes, and plenty of failures as well. And I'm sure at a conference 10 years from now, we'll be bemoaning the mistakes and flawed intentions of SOA. 

But chunk we must.

 

Topic: Tech Industry

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.

Talkback

1 comment
Log in or register to join the discussion
  • Interesting abstraction

    Chunking is an interesting abstraction of the process that is being undertaken in the selection of SOA. However, it seems flawed. SOA is not task-oriented, BPM is task-oriented. SOA is, as the name so correctly states, service-oriented. A service provides a common grouping of capabilities. The trick with developing a good SOA is thinking about how those services will be utilized within the organization.
    morgenthaljp