Tried to post yesterday, but Word locked up when I attempted to transmit to the blog site. Word 97, the jury is still out for me. Anyway, I did moderate the panel: Building an SOA that Scales. Here is the description: "The great thing about SOA is that you can start small. But how can you build to one set of requirements while keeping long-term SOA goals in mind? Here are the technology and governance issues to Tried to post yesterday, but Word locked up when I attempted to transmit to the blog site. Word 97, the jury is still out for me. Anyway, I did moderate the panel: Building an SOA that Scales. Here is the description: “The great thing about SOA is that you can start small. But how can you build to one set of requirements while keeping long-term SOA goals in mind? Here are the technology and governance issues to consider.” The panelist where: David Chappell, VP & Chief Technologist, SOA, Oracle John Daly, VP & GM, Global Architecture Services, Keane, Inc. Daniel M. Foody, VP of Actional Products, Progress Software W. George Glass, Chief Architect & Director, Platform Design & Build, BT Exact Eric Newcomer, CTO, IONA Technologies The takeaways from the panel where: Focus on the architecture as a holistic unit; make sure to consider all components. Keep in mind that your ability to scale is limited by your slowest component. Consider standards, but don’t let them lead you. Make sure you focus on what you need, and your requirements now, and into the future. Metadata and schemas need to be considered along with scalability, and abstraction layers provide additional agility. Here goes, I’m pressing the button. Software Development