Aditya Yadav & Associates

SOA is not about Technology its about how its designed and how it meets the changing needs of the business

---

Most Engineering Head's turn a SOA implementation into a Technology Mess. We believe that SOA or EAI is not about a mish-mash of technologies but rather about a good design that works for a particular company's systems and needs without creating an unmanageable White Elephant.  The first thing we do is to remove temporal dependencies and once that is achieved then we take it from there in phases. And we will always discuss with you when making choices between Reliable and Proven technologies and ones that push the boundary. Thats why our SOA works.

Intra company EAI and B2B EAI differ in aspects of control. In case of a Fortune 500 company with 100 subsidiaries its like a dictatorship and EAI could be simpler than one imagine's. We can work with you even if you have a democracy of sorts between companies and still need B2B-EAI.

SOAP (Tracker)

1. WS-Notification
2. WS-SOAPoverUDP
3. WS-Addressing
4. WS-Transfer
5. WS-Eventing
6. WS-Policy
7. WS-Discovery
8. WS-Metadata Exchange
9. WS-Resource
10.   WS-Security
11.   WS-Federation
12.   WS-Trust
13.   WS-SSO
14.   WS-Reliable Messaging
15.   WS-Reliability
16.   WS-Business Activity
17.   WS-Coordination
18.   WS-Transaction
19.   WS-BPEL
20.   WS-Management

Others...

1. BSON
2. Thrift
3. Protocol Buffer
4. Hessian
5. Etch
6. Hadoop Avro

Languages

1. .Net + Java (Primary Focus)
2. Python, C++, Ruby, Php (Secondary Focus)

1. Resource Oriented Architecture
2. Service Oriented Architecture
3. Messaging Oriented Architecture
4. Enterprise Mashups (Without using any Mashup Platform, Propreitary or Open Source)
   

The Rincci Contrarian Agile SOA Methodology

"80% of SOA projects fail to deliver value to the business"???
"It takes 10-15 years to get a SOA transition right"???
"To succeed with SOA you need excellent governance"???
"Purchasing bloated vendor SOA stacks is the key to SOA success"???

Corporate Governance led to IT Governance and have naturally made it to SOA governance. Do we know any other way? Can we draw parallels from the evolution of the internet and internet based systems, or open source systems which have evolved through worldwide collaboration and we cannot get SOA right with just 20-40 systems and teams in controlled office locations perhaps just 5-10 locations?

Can we have a SOA methodology which is agile enough to deliver rapidly on changing business needs instead of an ivory tower architecture? While a SOA is an ecosystem that is expected to deliver Strategic benefits while each system is expected to deliver Tactical benefits, can we deliver both without conflicts?

Is there a methodology that doesn't lead to power politics and doesn't need corporate restructuring? Can I get the best of the SOA Manifesto values, principles and practices and marry them with Agile techniques?

Rincci SOA is a Contrarian Agile Methodology evolved over most of the last decade, it is contrarian because it says (and hopefully shows) that it is not poor governance that causes SOA failures but rather governance itself is a single point of failure and a pessimistic organizational structure that causes SOA to fail. Rincci SOA has been tried at about 100 fortune and other global companies with virtually 100 percent success rates. Brought to you by Aditya Yadav & Associates. "Essays on SOA And EAI - A Pocket Guide" is the official bible of the Rincci SOA methodology. An easy read, short and succint collection of essays, with practical practices that can be adopted rightaway. Without any vendor speak and being agnostic to any Vendor Stack or Tools.