Documents » desventajas de soa.
Abstract: IT managers realize that service-oriented architecture (
SOA) projects are no longer an “if”—they’re a “when.”
SOA can help achieve your number-one goal: aligning IT with business. If you’re in the consideration and planning stage, you’ll need some practical strategies for a business-driven
SOA deployment. Find out how packaged solutions can accelerate
SOA deployments, ease the burden of
SOA management, and more.
PubDate: 6/19/2009 4:03:00 PM
Abstract: Before an organization can truly realize the cost and agility benefits of enterprise service-oriented architecture (SOA), there are a few concepts it should know about. By understanding the various stages of SOA adoption and by knowing what technologies are available, an organization will stand a better chance of succeeding in its SOA initiatives. With these seven steps, effective SOA can be realized.
Abstract: In the larger schema of things, SOA would espouse general, more abstract concepts of software reusability and encapsulation within certain boundaries (as to then provide access to that software via defined interfaces), Web services would then make these SOA concepts vendor-independent due to their use of generally accepted standards, while BPM and BPEL would be some of the engines making the whole system work.
Abstract: Corporate governance encompasses the processes and systems by which organizations operate—and it affects every business. To effectively participate in governance processes, businesses should consider closed-loop service oriented architecture (SOA). Although stand-alone applications for governance, management, and security exist, find out why they do not enable the demand and value management that closed-loop SOA offers.
Abstract: There’s no disputing the fact that content management systems (CMS) and service-oriented architecture (SOA) are closely related. From reuse, the ability to loosely couple service and functions, to being able to combine services into a new form, SOA and CMS share many common threads in the enterprise world. Find out how the forces that have made SOA so important today are now doing the same for CMS in web site management.
Abstract: In the past, full efficiency was almost impossible for most manufacturing sites thanks to lack of integration between plant systems and business systems. But that’s changing now, with the advent of enterprise service-oriented architecture (SOA). SOA allows you to change and improve your processes without expensive IT integration projects. Learn about the business opportunities SOA can create for you.
Abstract: Systems integration with service-oriented architecture (SOA) helps you reuse the functionality in your mainframe applications. Extending your mainframes to an SOA through Web services will accelerate your time to market, keep your costs low, and help you avoid undue risk. Keep your business dynamic and current, and stay competitive in today’s marketplace—modernize your existing mainframes with SOA.
Abstract: Anyone even peripherally exposed to business media that touch on enterprise application technology has seen the term service-oriented architecture (SOA) bandied about in advertisements and articles. Given the central role of SOA in information technology, it is important to get beyond a buzzword level understanding. There are three key concepts surrounding SOA: granularity, Web services, and change management.
Abstract: The battle for the dominance in service-oriented architecture (SOA) and Web services has nonetheless so far largely been a war of words without the clear winner yet (and not any time soon), as many underlying Internet-based standards have emerged only recently.
Abstract: The big buzzword in enterprise-wide package software is service-oriented architecture (SOA). SOA promises to solve a company's software ills, making life easier for information technology departments. This research note takes a look at this new architecture and highlights some concerns.
Abstract: Company employees, business partners, and customers all demand secure and low-response-time access to business applications—from wherever they are. While SAP addresses this need through its enterprise service-oriented architecture (SOA) solution, when security features are added the application response time is slower. So what’s the best way to test global SOA deployments? Read this white paper to find out.
Abstract: In order to meet the increasing need to extend services around the world, companies must be able to consolidate data centers and business applications while adhering to compliance rules and security regulations. While SAP addresses these business needs through its enterprise service-oriented architecture (SOA) solutions, the question of how to test these global enterprise SOA deployments still needs to be answered.
Abstract: While service oriented architecture (SOA)-based systems are great for re-using the existing IT infrastructure to implement newer business processes, they only help IT professionals. Thus, an SOA-based system is a technical answer to a business challenge—but in order to help businesses react to business changes, existing business rules management system (BRMS) technology should be included in the mix.
Abstract: The service-oriented architecture (SOA) integration framework enables organizations to map IT processes to business needs, with new business processes being defined on demand for business agility. However, SOA is predicated on an ability to integrate loosely-coupled services, one application to another: users are not necessarily involved. This creates challenges for governing how service assets are developed, provisioned, and invoked.
Abstract: Services-oriented architecture (SOA) is known for its building-block software design approach. Less commonly understood is the challenge of managing composite applications whose components are shared by multiple applications. The performance of these components varies with application demand, resulting in dramatic and unpredictable changes in application service levels. However, there is a cost-effective way to resolve the SOA application infrastructure dilemma.
Abstract: Although service-oriented architecture (SOA) provides greater flexibility for organizations, connectivity within SOA is a major issue, and must be addressed at an early stage. The use of a bus architecture provides a high level of abstraction, and minimizes the number of adaptors required, while data transformation and intelligent data mapping help to lower time spent on retro-testing and maintenance costs.
Abstract: As businesses move away from buying applications to buying the means of facilitating business processes, a different approach to technology assets is required. Service-oriented architecture (SOA) will enable organizations to run business from a process point of view. Tooling must therefore allow existing investments to be used within the SOA environment, enabling business processes to be easily and effectively modeled.
Abstract: Integration projects that attempt to fuse processes with application and system interfaces are likely to fail. A more pragmatic approach involves service-oriented architecture (SOA), where integration is determined by business requirements rather than technology factors. However, SOA alone is insufficient. Composite adapter services provide a layer of abstraction between service requestors and service providers, enabling cost-effective and versatile enterprise integration.
Abstract: Chief information officers keen to introduce service-oriented architecture (SOA) into their organization must deal with the many legacy applications that are potential roadblocks. To move to an SOA-enabled future, organizations have to service legacy applications, and evaluate which legacy application would give the best return on investment if modernized. The solution may be a process-oriented approach to legacy system transformation.