There has been no shortage of articles and blogs recently talking about the lack of success that companies are having with service-oriented architecture (SOA). While many people have seen the technology adoption curves from Gartner that show that all new technologies go through a “trough of disillusionment,” it still doesn’t prevent many people from proclaiming that all of the hype was unjustified and asking the question, “Does SOA really matter?”
Policy-based Governance Helps Security Take Its Rightful Place as Just Another Part of Your SOA Infrastructure
Haven’t we all caught ourselves thinking of security as primarily a technical problem? Recall the days when we asked, “How do I implement a PKI to secure my Web applications?” For security folks, those were the days. However, there’s been a sea change in the industry since those simpler times.
Large banking organizations are always looking to consolidate IT and improve business efficiency. Historically, banks have developed their business and their technology organically and reactively to meet immediate business needs that have led to extreme and uncoordinated complexity. In the past few years, the regulatory demands placed on banks in the form of MiFiD, Basel II, and Sarbanes-Oxley have clearly demonstrated that these complex environments are extremely difficult to manage and change.
Enterprise architecture is uniquely positioned to be a significant driver of an enterprise’s outsourcing decisions. However, two things are required: a service-oriented focus for the EA team and an understanding of the sourcing decision life cycle.
Between the Edge and the Hub
Ever since two applications were first plugged together, architects have debated where integration logic belongs: The Hub or the Edge.
Long before there was IT, there was Data Processing - a function most firms created to automate high volume tasks, such as creating bills and processing payments. Data Processing was centered around a mainframe that did much of its processing in batch. Then new architectures arrived and were leveraged by new ways of using ‘data processing’ - on-line transaction architectures, followed by client-server, followed by Internet-based architectures.