The Agile Architecture Revolution: How Cloud Computing, REST-based SOA, and Mobile Computing are Changing Enterprise IT
A sneak peek at upâ€“andâ€“coming trends in IT, a multidimensional vision for achieving business agility through agile architectures The Agile Architecture Revolution places IT trends into the context of Enterprise Architecture, reinventing Enterprise Architecture to support continuous business transformation. It focuses on the challenges of large organizations, while placing such organizations into the broader business ecosystem that includes small and midsize organizations as well as startups. Organizes the important trends that are facing technology in businesses and public sector organizations today and over the next several years Presents the five broad organizing principles called Supertrends: location independence, global cubicle, democratization of technology, deep interoperability, and complex systems engineering Provides a new perspective on serviceâ€“oriented architecture in conjunction with architectural approaches to cloud computing and mobile technologies that explain how organizations can achieve better business visibility through IT and enterprise architecture Laying out a multidimensional vision for achieving agile architectures, this book discusses the crisis points that promise sudden, transformative change, unraveling how organizations spending on IT will continue to undergo radical change over the next ten years.
Yogish Pai: One of the best practices for Enterprise Architecture teams to redo the enterprise road map on a periodic basis. It is typically reviewed and updated during the yearly budgeting cycle and my preference is to perform this activity every 18 months. The best practices (and the traditional approach) is to first document the as-is, next develop the target or future state (architecture) and finally develop a short term (6 months), mid term (12 months) and long term (18 months) road map. Preferable an actionable road map that ties back to the business initiatives.
Implementing Service Oriented Architecture at the Canada Institute for Scientific and Technical Information
Anthony, Stephen K. The Serials Librarian, 55(01-02), pp. 235 - 253. As they seek new roles in the digital realm, libraries are finding it increasingly difficult to manage the complexity of technology implementation while continuing to cost-effectively meet their mandates as information providers. Many organizations find themselves dealing with legacy, isolated, duplicated and ineffective information systems. The practices of enterprise architecture and service oriented architecture hold much promise as methodologies to reduce complexity, to encourage and enable collaborations, and finally to rein in the beast of technology. Even libraries under budgetary constraints can benefit from knowledge of enterprise architecture and service oriented architecture best practices.
Neil Ward-Dutton, July 24, 2008: Via Service Oriented Enterprise, I recently picked up an Infoworld blog post by SOA journeyman David Linthicum, where he makes a couple of very strange points about SOA and ESBs. It may be, of course, that the post is pure link bait: certainly, David appears to have said some relatively sane things in the past, so that might be it. If it is link bait, I'm going to fall for it now.
Draft 2.0 of The Open Group's SOA ontology. This draft is being exposed for comment outside The Open Group prior to formal Open Group company review. Interested parties are invited to sent comments, and those comments will be addressed in the version submitted to formal review by The Open Group. A PDF file contains the textual description of the ontology, and an OWL file contains the ontology itself.
Author Geoffrey Moore explains how SOAs will become the underlying force of the new data center.
Stew Welbourne: Yet more circular debate about whether SOA is just hype or whether it offers anything of value. It's addictive reading, not that I expect anyone to reach a definitive answer, but moreso to observe the correlation between the debating individual, the scope of his/her problem-space, and his/her corresponding position on whether SOA is hype or not. The relationship between Enterprise Architecture and SOA (and here I have just detatched a seprate thread about EA and Hype!!) is significant in my opinion as a result of the hugely important question of scope. The good old example of the difference between an Enterprise Architect and a System or Application Architect is the analogy with Town Planners and Building Planners. In simple terms Enterprise Architects are focusing at the optimal arrangement of buildings and utilities over a large area, whereas System/Application architects are focusing on the optimal construction of a small number of buildings and their optimal interfacing with the utilities they assume will be there at some point.
Service-Oriented Architecture (SOA) is a way of organizing software. If your companyâ€™s development projects adhere to the principles of SOA, the outcome will be an inventory of modular units called services, which allow for a quick response to change. This book tells the SOA story in a simple, straightforward manner that will help you understand not only the buzzwords and benefits, but also the technologies that underlie SOA: XML, WSDL, SOAP, XPath, BPEL, SCA, and SDO. And through it all, the authors provide business examples and illustrations, giving a practical meaning to abstract ideas.
This book demonstrates service-oriented architecture (SOA) as a concrete discipline rather than a hopeful collection of cloud charts. Built upon the author's firsthand experience rolling out a SOA at a major corporation, SOA in Practice explains how SOA can simplify the creation and maintenance of large-scale applications. Whether your project involves a large set of Web Services-based components, or connects legacy applications to modern business processes, this book clarifies how -- and whether -- SOA fits your needs.
Today, business processes and information systems are so tightly intertwined that they must be designed together, as parts of a total architecture, to realize enterprise goals. In Succeeding with SOA, Paul Brown shows how service-oriented architectures (SOAs) provide the best structure for such integration: clean, well-defined interfaces between collaborating entities. But even SOAs need to be correctly understood and implemented to avoid common failures. Drawing on decades of experience, Dr. Brown explains what business managers and IT architects absolutely need to know--including critical success factors--to undertake this essential work.
Information Technology professionals can use this book to move beyond the excitement of web services and service oriented architecture (SOA) and begin the process of finding actionable ideas to innovate and create business value. In Enterprise SOA: Designing IT for Business Innovation, SAP's blueprint for putting SOA to work is analyzed from top to bottom. In addition to design, development, and architecture, vital contextual issues such as governance, security, change management, and culture are also explored. This comprehensive perspective reduces risk as IT departments implement ESA, a sound, flexible architecture for adapting business processes in response to changing market conditions. Based on extensive research with experts from the German software company SAP, this definitive book is ideal for architects, developers, and other IT professionals who want to understand the technology and business relevance of ESA in a detailed way - especially those who want to move on the technology now, rather than in the next year or two.
In The New Language of Business, senior IBM executive Sandy Carter demonstrates how to leverage SOA, Web 2.0, and related technologies to drive new levels of operational excellence and business innovation. Writing for executives and business leaders inside and outside IT, Carter explains why flexibility and responsiveness are now even more crucial to successâ€“and why services-based strategies offer the greatest promise for achieving them. Youâ€™ll learn how to organize your business into reusable process componentsâ€“and support them with cost-effective IT services that adapt quickly and easily to change. Then, using extensive examples - including a detailed case study describing IBMâ€™s own experience - Carter identifies best practices, pitfalls, and practical starting points for success.
This book spells out guidelines and strategies for successfully using Service Oriented Architecture (SOA) in large-scale projects. SOA represents the latest paradigm in distributed computing and middleware development. However,SOA is not a revolution, but rather an evolution in software architecture. SOA is a collection of best practice software construction principles accompanied by proven methodologies in development and project management. This book is unique in that it offers a pragmatic approach to the topic. The authors borrow from their more than forty years of collective enterprise experience, and offer a frank discussion of the challenges associated with adopting SOA. They also help readers ensure that their organization does not become too closely tied to a specific technology. The result is a detailed introduction to the topic and an architectural blueprint for implementing SOA.
Targeted at management, the first six chapters of Secrets of SOA focus on the business impact of service-oriented architecture technological decisions with an emphasis on cost, flexibility, and the ability to maintain business objectives. Each of the six chapters explores a different topic that illustrates the value of a physically integrated SOA infrastructure organized at the enterprise level. Taken together, they demonstrate why enterprise-level planning, backed by a centralized deployment strategy, is essential to the success of SOA. Aimed at the IT executive, the second half of the book deals with specific IT issues raised by SOAs and why these issues are best dealt with on an enterprise level. Among the topics covered in these eight chapters are virtualizing resources, managing heterogeneous workloads, maintaining data and transactional integrity, and the value of proximity.
Authors Jason Bloomberg and Ronald Schmelzer - senior analysts for IT advisory and analysis firm ZapThink - say it all in the title of their new book, Service Orient or Be Doomed!: How Service Orientation Will Change Your Business. That is, if you fail to service orient your company, you will fail in competing with the organizations that do. This provocative new book takes service orientation out of its more familiar technological surroundings within service-oriented architecture and introduces it as a philosophy that advocates its rightful place within a business context, redefining it as a new way of thinking about organizing your business and its processes. Informal, challenging, and intelligent in style, Service Orient or Be Doomed!: How Service Orientation Will Change Your Business shows you how you can best use technology resources to meet your company's business goals and empower your company to go from stuck to competitive.
Companies face major challenges as they seek to flourish in competitive global markets, fuelled by developments in technology, from the Internet to grid computing and Web services. In this environment, service orientation - aligning business processes to the changing demands of customers - is emerging as a highly effective approach to increasing efficiency. In this book, Paul Allen provides an accessible guide to service orientation, showing how it works and highlighting the benefits it can deliver. The book provides an integrated approach: after covering the basics of service orientation, he discusses key issues such as business agility, designing quality-of-service infrastructure, implementing service-level agreements, and cultural factors. He provides roadmaps, definitions, templates, techniques, process patterns and checklists to help you realize service orientation. These resources are reinforced with detailed case studies, from the transport and banking sectors. Packed with valuable insights, the book will be essential reading for CIOs, IT architects and senior developers. IT facing business executives will also benefit from understanding how software services can enable their business strategies. Paul Allen is a principal business-IT strategist at CA and is widely recognized for his innovative work in component-based development (CBD), business-IT alignment and service-oriented architecture. With over thirty years experience of large-scale business systems, he is an established author whose previous book was the critically acclaimed 'Realizing e-Business with Components'. Sam Higgins is now with Forrester Research Inc.; formerly he managed the Innovation and Planning Unit of Queensland Transport's Information Services Branch. Paul McRae is the application architect in the Innovation and Planning Unit of Queensland Transport's Information Services Branch. Hermann Schlamann is a senior architect in the architecture group of Credit Suisse.
In this developerWorks Series book, IBM Enterprise Integration Team experts present a start-to-finish guide to planning, implementing, and managing Service-Oriented Architecture. Drawing on their extensive experience helping enterprise customers migrate to SOA, the authors share hard-earned lessons and best practices for architects, project managers, and software development leaders alike. Well-written and practical, Service-Oriented Architecture Compass offers the perfect blend of principles and "how-to" guidance for transitioning your infrastructure to SOA. The authors clearly explain what SOA is, the opportunities it offers, and how it differs from earlier approaches. Using detailed examples from IBM consulting engagements, they show how to deploy SOA solutions that tightly integrate with your processes and operations, delivering maximum flexibility and value. With detailed coverage of topics ranging from policy-based management to workflow implementation, no other SOA book offers comparable value to workingIT professionals. Coverage includes SOA from both a business and technical standpointâ€“and how to make the business case; Planning your SOA project: best practices and pitfalls to avoid; SOA analysis and design for superior flexibility and value; Securing and managing your SOA environment; Using SOA to simplify enterprise application integration; Implementing business processes and workflow in SOA environments; Case studies in SOA deployment; and After you've deployed: delivering better collaboration, greater scalability, and more sophisticated applications
This is a comprehensive tutorial that teaches fundamental and advanced SOA design principles, supplemented with detailed case studies and technologies used to implement SOAs in the real world. All major software manufacturers and vendors are promoting support for SOA. As a result, every major development platform now officially supports the creation of service-oriented solutions. Parts I, II, and III cover basic and advanced SOA concepts and theory that prepare you for Parts IV and V, which provide a series of step-by-step how to instructions for building an SOA. Part V further contains coverage of WS-* technologies and SOA platform support provided by J2EE and .NET.
Mashup Corporations: The End of Business As Usual tells the tale of Vorpal Inc., a company that pioneers the implementation of service-oriented architecture to transform its business model. CEO Jane Moneymaker believes in marketing manager Hugo Wunderkind's idea of creating a new market using non-traditional methods based on mashups, but struggles to achieve this vision. The story illustrates what it takes to achieve cultural change, overturning established business and IT structures. By embracing a service-oriented approach Moneymaker makes Vorpal faster, flexible and more responsive, bringing an end to business as usual. Mashup Corporations takes a unique approach to communicating its message. From the first page, readers will find themselves in a story populated with people who interact in ways that will ring true to others who have struggled to make technology work in an organization, large or small. The conflicts that naturally arise between CEOs, CIOs, and line of business managers illustrate the important issues at stake within Vorpal and most other companies. As the leaders of Vorpal find their way out of their predicament, rules about how mashups and service orientation can be properly applied emerge. These rules, which may be the most enduring contribution of the book, are illustrated and analyzed using real-life examples.
The Role of Event Processing in Modern Business. In eBizQ, 30 July 2007. By Dr. K. Mani Chandy, Simon Ramo Professor of Computer Science, California Institute of Technology and Roy Schulte, Vice President and Distinguished Analyst, Gartner, Inc. Almost everyone wants to have an adaptive enterprise, a company that runs faster and smarter because it has "situational awareness," can "sense-and-respond" to opportunities and threats, and can "track-and-trace" items as they go through their life cycles. What do these three capabilities have in common? They are all achieved through event processing.
Service-Oriented Architecture (SOA): A Planning and Implementation Guide for Business and Technology
Amazon: The book shows you how to plan, implement, and achieve SOA value through its prescriptive approach, joining the business and strategic perspective to the technical and architectural perspective. Applicable to all industries, technology platforms, and operating environments, this innovative book provides you with the essential strategies to drive greater value from your SOA and realize your business goals.
By Darryl K. Taft, 15 July 2007. Dan Cahoon was looking for a way to streamline staffing operations at tax company H&R Block, the nation's largest seasonal employer. Rather than use traditional desktop-based software for the job, the senior systems architect at H&R Block was able to deliver SOA-connected AJAX portlets to more than 12,000 branch offices for temporary work spaces to meet the company's staffing needs.
Jesus Rodriguez and Javier Mariscal, @ SOA WORLD MAGAZINE. A well-planned Web Service interoperability environment begins by clearly defining who your Web Service consumers are now and in the future. There was a time not so long ago when you could count on a fairly homogenous consumer population. This was about the same time that you were happy just to be able to get a Web Service running in the first place and finding a consumer who could actually interact with your Web Service was cause for celebration. Those days have changed however and Web Services interoperability, once a "fancy" addition to your SOA design, is now a key and indispensable requirement in most SOA scenarios.
By Anant Kadiyala. SOA WORLD MAGAZINE, Jun. 28, 2007. With the emergence of Web 2.0 and SOA technologies, mashups have gained in popularity. Web 2.0 provides a rich user experience, and SOA technologies facilitate the underlying flexible plumbing required to make mashups happen. So you could say mashups are a mashup of Web 2.0 and SOA!
Book by Steve Jones published on Sep 26, 2006 by InfoQ. Major changes in technology have not been driven by the technologies themselves but by the change in thinking that they enabled. OO design changed software by changing thoughts away from procedures and onto real world "things". This book argues that for SOA to succeed we must move our thoughts away from the implementation technologies and towards the "what" of the business. Using a straight-forward, pictorially driven, methodology the book explains who to discover what the business services really are and how to construct an overall business service architecture.