CODEWITHSUNDEEP
wcfentity-frameworkdesign-patternssoa
user702769
user702769

Reputation: 2445

WCF + EF(POCO): Should I use SOA or are there alternative arhitectural styles?

I know almost nothing about SOA or anything about different arhitectural styles in general, so my questions may be completelly off or too generic

a) When creating WCF + EF (POCO), what are my options as far as the arhitectural style goes? One option is to implement WCF+EF app using SOA patterns, but what are alternatives to SOA?

b) I'm also a bit confused about how to decide whether to use SOA or whether to go with some alternative style ( I don't want to read through five or more books on SOA, only to find out it was a fad or a niche or not the best option for majority of my WCF + EF apps)?

Thank you

Upvotes: 1

Views: 1336

Answers (1)

Heretic Monkey
Heretic Monkey

Reputation: 12113

There's a lot of confusion over the term "SOA", much like any number of other acronyms our industry loves so much. It's really a way of getting applications to talk to one another. Thus, my initial confusion. WCF+EF could be one part of a larger service-oriented architecture, allowing other services to communicate with your service, all of which combine into the final application(s). I don't know that there's a way of "implementing WCF using SOA", since WCF is a single service point. You can use it to talk to other WCF services (even in the same service, if you're feeling adventurous), or you can use it to talk to a message bus or a mapping service, etc.

Hope that helps

Upvotes: 2

Related Questions