soa

What is service-oriented architecture? SOA is way to develop service oriented applications and WCF is technology which can be used to develop service oriented applications. BUT SOA defines strict rules (known as SOA tenets) for applications. If you don't follow these rules you are building services but these services do not conform to SOA. WCF allows you to develop plenty of types of services. You can develop interoperable SOAP services which conform to SOA or which doesn't. You can develop pure .NET services with non interoperable features and you can develop REST services. Moreover in SOA

Please let me know, ever so gently, if I am totally mangling the DDD concept, but here is my dilemma. Let's say I have the following domain model: Teacher IList<Class> Class Teacher IList<Student> Student Class Now, from a DDD perspective, it seems like the Teacher is my root, and indeed, in a simple app, I might carry around my Teacher with her classes and students and act on them as needed. But in an SOA situation, let's say I've pulled down my Teacher, her classes and students for display purposes (as dtos), and she wants to add a student. Surely I am not going to send the whole object

I am a novice in WCF and SOA. I am just starting out on these, I have a theoretical doubt: Client A has called a service and the logic is currently executing on the server. While the logic is executing, another call from Client B comes in for the same service. At this point what happens to the logic that is being executed for Client A? How does the service manage to serve both the requests? Answer to your question depends on binding you are using. There are two settings controlling this behavior: InstanceContextMode and ConcurrencyMode. Both these settings are set in ServiceBehaviorAttribute.

In some enterprise-like project (.NET, WCF) i saw that all service contracts accept a single Request parameter and always return Response : [DataContract] public class CustomerRequest : RequestBase { [DataMember] public long Id { get; set; } } [DataContract] public class CustomerResponse : ResponseBase { [DataMember] public CustomerInfo Customer { get; set; } } where RequestBase/ResponseBase contain common stuff like ErrorCode, Context, etc. Bodies of both service methods and proxies are wrapped in try/catch, so the only way to check for errors is looking at ResponseBase.ErrorCode (which is

Imagine we have 2 services: Product and Order. Based on my understanding of SOA, I know that each service can have its own data store (a separate database, or a group of tables in the same database). But no Service is allowed to touch the data store of another Service directly. Now, imagine we have stored the product and order data independently inside Product and Order Services. In the Order Service, we can identify products by their ID. My question is: With this architecture, how can I display the list of orders and product details on the "same" page? My understanding is that I should get

When I read docs about repositories, it is often to work with entities & collection but in a "read-only" manner. There are never examples where repositories have methods like insertUser(User $user) or updateUser(User $user) . However, when using SOA, Service should not be working with Entity Manager (that's right, isn't it?) so: Should my service be aware of the global EntityManager? Should my service know only about the used Repositories (let's say, UserRepository & ArticleRepository) From that both questions, another one, should my service ever explicitly persist() & flush() my entities ?

Heroku describes logs in its Twelve-Factor App manifest as simple event streams: Logs are the stream of aggregated, time-ordered events collected from the output streams of all running processes and backing services. Logs in their raw form are typically a text format with one event per line (though backtraces from exceptions may span multiple lines). Logs have no fixed beginning or end, but flow continuously as long as the app is operating. Additionally, apps should simply write logs to stdout , leaving the task to the "environment". A twelve-factor app never concerns itself with routing or

Call me a troll if you want, but I'm serious: how exactly is the new SOA trend any different than the client-service architecture that I was building 15 years ago? I keep hearing SOA but I don't see how it's different than what we've always done. Back 10 years ago, my company had multiple clients (in multiple languages) which talked to the same service. It wasn't XML (it was a binary protocol called Microsoft DCOM) and there wasn't auto-discovery through WSDL but that's OK since reading the docs was just as easy. Our system was even "open" in the sense we documented it enough to allow 3rd

基于组件的编程一直是软件业简化编程和提高效率和质量的一个重要方法，但是往往对于不同语言我们有不同的组件模型，从而需要不同的调用方式。SCA的目的是使用户在构建企业应用时有一个不再直接面对具体的技术细节的层次，而是通过服务组件的方式来构建应用。这种方式也使得客户的企业应用具有良好的分层架构，能够很好的分离应用的业务逻辑和IT逻辑，不但易于应用的构建，也易于应用的更改和部署。 SCA全称Service Component Architecture，即服务组件框架。服务组件体系结构 (SCA) 是一个规范，它描述用于使用 SOA 构建应用程序和系统的模型。它可简化使用 SOA 进行的应用程序开发和实现工作。它由BEA、IBM、Oracle等知名中间件厂商联合制定的一套符合SOA思想的规范。 SCA是一个可执行的模型，用于将不同的 服务集成到一个业务解决方案。它简化了实现业务服务的组件编程模型，这些组件可以使用不同编程语言实现,对于企业应用，SCA还提供了关键的一些基础设施，像安全性、事务、可靠调用等，这对于企业应用的开发而言就变得很方便了。SCA确实可以成为企业应用开发的利器SCA确实可以成为企业应用开发的利器。SCA是第一项承诺提供一个组合模型以启用服务网络并支持构建下一代面向服务应用程序的技术。 SCA在2005年11月，发布了0.9版本的规范，其中包括了组装模型规范，Java/C+

While reading SOA articles I came across an article in http://www.ibm.com/developerworks/websphere/library/techarticles/0806_boughannam/0806_boughannam.html . This explains about a Semantic/Logical service. There is an example of "request for organization data coming from sales department". This approach helps in overcoming the silos concept. I was wondering whether there is any WCF implementation similar to the architecture mentioned in the article. Though I made some search, I could not find out one. Could you please provide details of such an implementation or provide a reference to a