soa

I'm searching for a simple registry which provides a very simple API and works with resources that can be described as JSON. I'm designing a Resource Oriented Architecture (entirely HTTP REST, no WS-*'s ESB or other things, all communications are made over network, are stateless and all services share nothing) that will be all talking using JSON as primary data, so I'm a bit bored to use XML only to work with that SOA Registry. Disclaimer: I really love WSO2 stuff, I learned SOA looking at what they provide. The reason I didn't choose their registry is because from samples I've looked at it

I have to performance/load test a bunch of interdependant services. They all use net.tcp and most use duplex contracts and internal queueing. [handrolled POCO queue class using lock(syncRoot) { if(queue.Empty) Thread.Wait(); }] Here's the approach I've come up with: Identify WCF Services to be performance tested Identify the relavant Performance counters for each of the Services Identify the logical startpoint that would take the execution through the services being tested Auto Generate Unit Tests using VS.Net for each of the services Write specific Functional Tests (For example, I can take a

I'm working on an application that uses WCF to communicate between server and clients Server has changing number of services, along with one master service that clients can query for information about other services, and then subscribe to those they want using information from master service. Master service sends notifications to subscribed clients, when sub-services change (added, removed, etc) Also sub-services send notifications every few seconds. This sounds like a great opportunity for using WCFs Callback channels, however, they require you to use session. Also when sending notifications

While learning from @tereško's answer on how should a model be structured, I can't find what is the best way for communication between the services. I also found this answer which is a similar situation I'm dealing with, but the example is great for showcase. So, in that sense, how do I retrieve the recognition service inside of a Blog service for example, when the service has only access to a domain and mapper factory objects. Do I send it from the controller? Or do I need to send a service factory too? Update : I did not provide an example since I mentioned that the second answer of tereško

The Service layer is supposed to be on top of the Model layer. As such, models are not supposed to call services. However, I'm facing a situation where I need to, for example: interface Component { getResult(); } class Number implements Component { private value; public getResult() { return value; } } class Addition implements Component { private component1; private component2; public getResult() { return component1->getResult() + component2->getResult(); } } class ConstantFromExternalSource implements Component { private identifier; public getResult() { // call a service for fetching constant

Everyone's saying "Contract-First" approach to design WS is more inclined to SOA style design. Now, if we take the available open-source frameworks available to achieve that we have Spring-ws and also Axis2 (which supports both styles). I have a task to design SOA based e-commerce app. where loose coupling, quick response, security and scalability are the key points. So it is very important to choose the right framework from the start. Based on past experiences, which of them or something else do you guys think to be a more appropriate option for my requirements. That is a tough question. I

I've had a WCF Data service published for about 2 months. It's 100% been hacked already. I even noticed the service published on twitter! Luckily my site was under development and the user entity was only about 80 beta testers. Still this is a pretty big problem. With the power of E.F. Navigation properties anyone can easily write a script to download all my user data and my valuable domain data that no-one else has. I want to provide non-authenticated access and do things like: Limit what columns get exposed (e.g. a users emails) Limit number of requests possible per day (e.g. 10 per request