Email Alerts
-
Ten ways to identify services
SOA is increasingly becoming an unavoidable part of project delivery for many organizations. It is therefore high time that practitioners avoid the dangerous practice of creating ad-hoc services and begin following proven industry principles and meth... Tip
-
Forensic SOA
Jason Bloomberg discusses the legal ramifications of unhappy results with SOA implementations, a growing business for the experts at ZapThink. Tip
-
Project Zero, a RESTful new beginning for IBM
IBM has entered the world of RESTful Web services and scripting languages like Groovy and PHP with Project Zero. William Brodgen digs into the details of how it works. Tip
-
The "S" in "SOA" is services
David Linthicum discusses how the quality of services defines how well SOA can be implemented and governed. Tip
-
The service orientation of … everything
Those who claim SOA is nothing new are right. It borrows from engineering best practices that are universally deployed in the manufacturing sector. Tip
-
Why big consulting is hurting SOA
David Linthicum discusses how and why big consulting firms are hurting the implementation and perceptions in regards to service-oriented architecture. Tip
-
If you're in a hole, the first thing you do is stop digging
This chapter, excerpted from Service Orient or Be Doomed, discusses how to go about IT decision making processes in a business setting. Tip
-
Web Services: A Realization of SOA
Service-oriented architecture (SOA) represents an abstract architectural concept. It's an approach to building software systems that is based on loosely coupled components (services) that have been described in a uniform way and that can be discovere... Tip
-
Web services, Java and XA for distributed transactions
This tip delves into how Web services specifications, Java standards and XA protocols can be used to support business data transactions, perhaps as part of a federated system. Tip
-
Will SOA flexibility compromise your security?
Service-oriented architecture makes for a wonderful silo buster, but how do you lock down distributed Web services when the security domain is traditionally built around the application itself? Tip