Common Myths about SOA [Service Oriented Architecture]
-
Myths about SOA (Service Oriented Architecture) 1. SOA is a technology 2. SOAs require Web Services 3. SOA is new and revolutionary 4. SOA ensures the alignment of IT and business 5. A SOA Reference Architecture reduces implementation risk 6. SOA requires a complete technology and business processes overhaul 7. SOA requires an army of consultants 8. We need to build a SOA Facts 1. SOA is a design philosophy independent of any product, technology or industry trend 2. SOAs may be realized via web services but using web services will not necessarily result in a SOA 3. EDI, CORBA and DCOM were conceptual examples of SO 4. SOA is not a methodology 5. SOAs are like snowflakes – no two are the same. 6. SOA should be incremental and built on your current investments 7. Tools, not consultants 8. SOA is a means, not an end Deliver a solution, not a SOA This was somewhat an eye opener to me , since in my company , there had been a lot of discussion of creating a service oriented archtecture * by John Evdemon Architect, Architecture Strategy Microsoft
Omit Needless Words - Strunk, William, Jr.
Web based Project Management
Universal DBA | Ajax Rating | ExplorerTree | Globalization in 20 minutesAmen brother, I did some work last year building an application using SOA. There are several books describing service oriented architecture and they all tell the same thing (At least the ones that I read). It's a way of designing applications and services and not a technology. And to proof point 2 on the list, here's some examples of how I designed and implemented small size Service Oriented Applications: - Using Java RMI - Using .NET remoting - Using Sonic ESB 6.1 - Using Webservices These examples are all technologies that can be used in a solution using SOA.
WM. What about weapons of mass-construction?
-
Amen brother, I did some work last year building an application using SOA. There are several books describing service oriented architecture and they all tell the same thing (At least the ones that I read). It's a way of designing applications and services and not a technology. And to proof point 2 on the list, here's some examples of how I designed and implemented small size Service Oriented Applications: - Using Java RMI - Using .NET remoting - Using Sonic ESB 6.1 - Using Webservices These examples are all technologies that can be used in a solution using SOA.
WM. What about weapons of mass-construction?
Great there is a brilliant book on SOA by Thomas Erl Here[^] which i am hooked to right now . What other resources you found useful in your implementation ?
Omit Needless Words - Strunk, William, Jr.
Web based Project Management
Universal DBA | Ajax Rating | ExplorerTree | Globalization in 20 minutes -
Great there is a brilliant book on SOA by Thomas Erl Here[^] which i am hooked to right now . What other resources you found useful in your implementation ?
Omit Needless Words - Strunk, William, Jr.
Web based Project Management
Universal DBA | Ajax Rating | ExplorerTree | Globalization in 20 minutesThey gave me and my fellow students a dozen presentations on the subject. They were helpfull, but they focused too much on one product. The documentation on MSDN Patterns and Practices is quite good too, especially if you're working in a .NET environment.
WM. What about weapons of mass-construction?
-
When the first thing is you think this post is talking about is a Start of Authority DNS record.
Jeremy Falcon A multithreaded, OpenGL-enabled application.[^]
Jeremy Falcon wrote:
When the first thing is you think this post is talking about is a Start of Authority DNS record
I guess it is industry specific.... First thing I thought of was "Speed Of Advance/Speed Of Approach" the next thing that came to mind was "Special Operations Aircraft" and I ruled out "Strategic Offensive Arms" pretty fast... but none of those really fit....
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
:confused: :confused:
Chris Meech I am Canadian. [heard in a local bar] Nobody likes jerks. [espeir] Hey, I am part of a special bread, we are called smart people [Captain See Sharp] The zen of the soapbox is hard to attain...[Jörgen Sigvardsson] I wish I could remember what it was like to only have a short term memory.[David Kentley]
-
Jeremy Falcon wrote:
When the first thing is you think this post is talking about is a Start of Authority DNS record
I guess it is industry specific.... First thing I thought of was "Speed Of Advance/Speed Of Approach" the next thing that came to mind was "Special Operations Aircraft" and I ruled out "Strategic Offensive Arms" pretty fast... but none of those really fit....
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
Jeffry J. Brickley wrote:
I guess it is industry specific....
Probably. On an aside, fortunately nobody wants me as an admin anymore since I don't have much Active Directory experience, and I like it fine that way (of course, it's not like I look for many admin jobs, even on Unix). :-D
Jeremy Falcon A multithreaded, OpenGL-enabled application.[^]
-
It is what's left over after you scrub your application with AJAX. Geez don't you know anything? :-D
led mike
:laugh:
Omit Needless Words - Strunk, William, Jr.
Web based Project Management
Universal DBA | Ajax Rating | ExplorerTree | Globalization in 20 minutes -
Jeffry J. Brickley wrote:
I guess it is industry specific....
Probably. On an aside, fortunately nobody wants me as an admin anymore since I don't have much Active Directory experience, and I like it fine that way (of course, it's not like I look for many admin jobs, even on Unix). :-D
Jeremy Falcon A multithreaded, OpenGL-enabled application.[^]
Jeremy Falcon wrote:
since I don't have much Active Directory experience
Darn and I was hoping to draft you here to fix the active directory. ;P
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
Myths about SOA (Service Oriented Architecture) 1. SOA is a technology 2. SOAs require Web Services 3. SOA is new and revolutionary 4. SOA ensures the alignment of IT and business 5. A SOA Reference Architecture reduces implementation risk 6. SOA requires a complete technology and business processes overhaul 7. SOA requires an army of consultants 8. We need to build a SOA Facts 1. SOA is a design philosophy independent of any product, technology or industry trend 2. SOAs may be realized via web services but using web services will not necessarily result in a SOA 3. EDI, CORBA and DCOM were conceptual examples of SO 4. SOA is not a methodology 5. SOAs are like snowflakes – no two are the same. 6. SOA should be incremental and built on your current investments 7. Tools, not consultants 8. SOA is a means, not an end Deliver a solution, not a SOA This was somewhat an eye opener to me , since in my company , there had been a lot of discussion of creating a service oriented archtecture * by John Evdemon Architect, Architecture Strategy Microsoft
Omit Needless Words - Strunk, William, Jr.
Web based Project Management
Universal DBA | Ajax Rating | ExplorerTree | Globalization in 20 minutesI wasn't aware that there were very many programmers that were so confused about SOA. And business people not understanding the reality behind the buzzwords is nothing new.
Logifusion[^]
"This isn't a business. I've always thought of it as a source of cheap labor. Like a family." -
It is what's left over after you scrub your application with AJAX. Geez don't you know anything? :-D
led mike
led mike wrote:
It is what's left over after you scrub your application with AJAX.
Scum Of Application? Yuck! :-D
Author of The Career Programmer and Unite the Tribes www.PracticalStrategyConsulting.com
-
Myths about SOA (Service Oriented Architecture) 1. SOA is a technology 2. SOAs require Web Services 3. SOA is new and revolutionary 4. SOA ensures the alignment of IT and business 5. A SOA Reference Architecture reduces implementation risk 6. SOA requires a complete technology and business processes overhaul 7. SOA requires an army of consultants 8. We need to build a SOA Facts 1. SOA is a design philosophy independent of any product, technology or industry trend 2. SOAs may be realized via web services but using web services will not necessarily result in a SOA 3. EDI, CORBA and DCOM were conceptual examples of SO 4. SOA is not a methodology 5. SOAs are like snowflakes – no two are the same. 6. SOA should be incremental and built on your current investments 7. Tools, not consultants 8. SOA is a means, not an end Deliver a solution, not a SOA This was somewhat an eye opener to me , since in my company , there had been a lot of discussion of creating a service oriented archtecture * by John Evdemon Architect, Architecture Strategy Microsoft
Omit Needless Words - Strunk, William, Jr.
Web based Project Management
Universal DBA | Ajax Rating | ExplorerTree | Globalization in 20 minutesSOA is a means, SOA is not a methodology, no two are the same soooooo... nope, stil don't know what a SOA is. but that's OK, i don't want to ! it sounds like more management handwaving, to me.
-
I wasn't aware that there were very many programmers that were so confused about SOA. And business people not understanding the reality behind the buzzwords is nothing new.
Logifusion[^]
"This isn't a business. I've always thought of it as a source of cheap labor. Like a family." -
SOA is a means, SOA is not a methodology, no two are the same soooooo... nope, stil don't know what a SOA is. but that's OK, i don't want to ! it sounds like more management handwaving, to me.
Chris Losinger wrote:
management handwaving
:badger:
Author of The Career Programmer and Unite the Tribes www.PracticalStrategyConsulting.com
-
Jeremy Falcon wrote:
since I don't have much Active Directory experience
Darn and I was hoping to draft you here to fix the active directory. ;P
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
Jeffry J. Brickley wrote:
Darn and I was hoping to draft you here to fix the active directory.
Ahem, I could *pretend* to fix it. I have a BS in BS. :)
Jeremy Falcon A multithreaded, OpenGL-enabled application.[^]
-
Chris Losinger wrote:
management handwaving
:badger:
Author of The Career Programmer and Unite the Tribes www.PracticalStrategyConsulting.com
:jig: - i'm managing! :badger: - me too!
-
Myths about SOA (Service Oriented Architecture) 1. SOA is a technology 2. SOAs require Web Services 3. SOA is new and revolutionary 4. SOA ensures the alignment of IT and business 5. A SOA Reference Architecture reduces implementation risk 6. SOA requires a complete technology and business processes overhaul 7. SOA requires an army of consultants 8. We need to build a SOA Facts 1. SOA is a design philosophy independent of any product, technology or industry trend 2. SOAs may be realized via web services but using web services will not necessarily result in a SOA 3. EDI, CORBA and DCOM were conceptual examples of SO 4. SOA is not a methodology 5. SOAs are like snowflakes – no two are the same. 6. SOA should be incremental and built on your current investments 7. Tools, not consultants 8. SOA is a means, not an end Deliver a solution, not a SOA This was somewhat an eye opener to me , since in my company , there had been a lot of discussion of creating a service oriented archtecture * by John Evdemon Architect, Architecture Strategy Microsoft
Omit Needless Words - Strunk, William, Jr.
Web based Project Management
Universal DBA | Ajax Rating | ExplorerTree | Globalization in 20 minutes -
Jeffry J. Brickley wrote:
Darn and I was hoping to draft you here to fix the active directory.
Ahem, I could *pretend* to fix it. I have a BS in BS. :)
Jeremy Falcon A multithreaded, OpenGL-enabled application.[^]
Jeremy Falcon wrote:
Ahem, I could *pretend* to fix it. I have a BS in BS.
Sorry... this is contractor side... you need real qualifications. ;P
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
SOA is a means, SOA is not a methodology, no two are the same soooooo... nope, stil don't know what a SOA is. but that's OK, i don't want to ! it sounds like more management handwaving, to me.
Chris Losinger wrote:
SOA is a means, SOA is not a methodology, no two are the same
well.... if you think Strategic Offensive Arms. ;)
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
Jeremy Falcon wrote:
Ahem, I could *pretend* to fix it. I have a BS in BS.
Sorry... this is contractor side... you need real qualifications. ;P
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
Jeffry J. Brickley wrote:
you need real qualifications.
You kiddin? BS can take you to the top, didn't ya know? :-D
Jeremy Falcon A multithreaded, OpenGL-enabled application.[^]
-
Jeffry J. Brickley wrote:
you need real qualifications.
You kiddin? BS can take you to the top, didn't ya know? :-D
Jeremy Falcon A multithreaded, OpenGL-enabled application.[^]
Jeremy Falcon wrote:
BS can take you to the top, didn't ya know?
only if you have a really strong nose and good swimming arms. :laugh:
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)