OOPS Design Patterns and Principles. Service Orientated Architecture (SOA\WCF) explained and defined for Executives. Service Orientated Architecture (SOA) is a big business buzzword tossed into conversations at board meetings and at executive briefings.
At this level, however, SOA really refers to connecting disparate systems across application, department, corporate, and even industry boundaries. This is the “Big” SOA concept, and this is the realm of the enterprise architect, and the space of million dollar Service Bus applications, SAP systems and other wonderful products. Unfortunately the fact still remains that a chain is a strong as its weakest link, if the systems hooked up to the top of the range Service Bus are not rock solid and can not be trusted to produce the correct results all the time, then the some of the true potential of the investment is lost.
I call SOA at the application level “Little” SOA. Cloud Computing - Windows Azure for Enterprises. Cloud computing has already proven worthy of attention from established enterprises and start-ups alike.
Most businesses are looking at cloud computing with more than just idle curiosity. As of this writing, IT market research suggests that most enterprise IT managers have enough resources to adopt cloud computing in combination with on-premises IT capabilities. Of course, there are people who are skeptical of cloud computing’s ability to deliver on the promises.
This emerging solution is almost analogous to the creation of ARPANET (precursor to Internet); many skeptical research institutions didn’t want to join the initial network for fear of losing their private data. Once scientists saw the benefits of data networking and the collaboration it enabled, there was no stopping them, and the rest is history. Cloud Computing Azure, Amazon Web Services, Google App Engine and Force.com are a few examples of public clouds. Figure 1 Azure Is a PaaS Offering Software as a Service Azure Compute <? SOA: How to design a service - Inside Architecture. I find myself in the situation of having to set down a design standard for SOA services.
The thing is: SOA Services are much more than a technical artifact. They are a solution to a business architecture requirement for shared services, and the business architecture needs to exist first, or at least be tacitly understood and described, in order for the service to have any lasting value. So, first step in designing a SOA Service is to refer to the business process diagrams that your business architect has produced.
For each interaction between roles, look for the data needed to make decisions. For example, if you are looking at the process flow for a new purchasing agreement, you may see steps where three different collaborating systems need data. You are collecting data for your service contract. What is the responsibility of the service? The second question above: "how will your actors be authenticated," must be answered. OK. The data points you need for the service contract are: Are Your Software Licenses Cloud-Friendly? ZapThink likes nothing better than to poke a stick at a hornets’ nest, and our last ZapFlash did not disappoint.
We discussed how private Clouds weakened the enterprise value proposition for Cloud Computing, eliciting consternation far and wide, not from enterprises implementing such Clouds, but from consultants and vendors in the business of building and outfitting them. To which we say: well, duh! Cloud Computing is a paradigm shift precisely because we won’t need to hire pricey consultants or buy a lot of gear to use them! In fact, enterprise software vendors are running scared. Cloud Computing represents an enormous threat to their entire business model, and they’re fighting it every step of the way.
In this ZapFlash I’m talking specifically about the heavyweight enterprise apps here—Enterprise Resource Planning (ERP), Customer Relationship Management, Supply Chain Management and their brethren. So far so good, but here’s where things get complicated. Image credit: Joelk75. WSO2Con 2011 - Keynote : Service Orientation. SOA. How to Stop Writing Next Year's Unsustainable Piece of Code. All of Anne Thomas Manes' Content on InfoQ.