Think a about a common scenario like deploying a new server: if this process is 15 days long because we need to fulfill some absurd process steps,in the end the OS of the deployed platform does it really can change the “weight” of the process?(Maybe you can’t deploy a new server because you need a license…so your process is “bounded” by the technology chosen…)

For sure the tech-stack you choose have to support your architectural-processes(in the tech-point of view of course,but not only), but probably if the process are agile and effective the technologies used are less central.
Today we see the technology stack as the central point because we adapt the processes to the technology and not vice-versa, and probably old technologies embody old processes and way of thinking.

Is time mature for a POA? is Process Oriented Architecture the evolution of SOA?

(..In my heart I’m always a buzzword lover;))

• 90% of “ordinary” programmers, just trying to do their work(hopefully…)
• 10% of “extraordinary” programmers, they want to lead and demonstrate that they’re faster,clever, better, anything ${whatyouwant}er

So the “e” leads the development community finding “genius” solutions, by doing black magics frameworks, and they are passionate, and thats is a good thing… but this produce what I call the Inverse Frameworks Factor! 90% of the frameworks are for the 10% of programmers… and ,you know, given the previous division of programmers..(no, I’m not going to list them all…)

That’s not secret… Think about how many projects you have seen messed up by the complexity of the problem and how many by the complexity of the “not-so-usefull-but-cool-enterprise environment”.  What are the results?