More on CRUD…

Maarten just published a draft of his upcoming article “CRUD, only when you can afford it”

0

Services and CRUD

If a service provides you with CRUD you can directly manipulate fields of entities or entity-views. This is as straight forward as possible, but why isn’t it always the best thing to do? Here is an analogy: The argument against CRUD is very similar to the one against functional programming using C structs versus object…

0

Who is responsible for a service contract?

The majority of architects agree on the contract first approach. But who is actually responsible for the contract definition and who owns it? Is it the developer, the architect or the business analyst? Being responsible for the contract implies understanding the contract. Given the fact that service boundaries are defined by Web Services technologies, the…

1

Maarten on concurrency…

Maarten Mullender has just published his new article about service interaction and concurrency on msdn. Curious? Here’s the summary:   “Create and work with software services and service interactions using design principles that will give you several ways to deal with the challenges of keeping data valid when consumers retrieve and work with the data…

1

And You Thought You Knew about Web Services?!

The TechEd session voting demanded an additional slot for our Web Services Chalk-&-Talk (CHT011)! It’s great that so many people care about the way Web Services should be used in a service oriented fashion. If you’re going to attend the session and have a specific question, just add a comment to my blog… Hope to…

5

Preparing for TechEd 2004 Europe

After being quiet for a while, I’m back (at least for this post ;-). I was very busy during the last couple of weeks: A lot of architectural design sessions, presentations and last but not least preparing my three sessions at TechEd Europe: If you’re interested in Web Services, interoperability or service orientation, these sessions are…

3

Web Services Quiz: Issue 8 – the Answer

The number one problem in dealing with rpc-literal Web Services is the fact that they are unsupported on the .NET platform, yet. However, every rpc-literal message can be “built” using a doc-literal based implementations. By doing so, the .NET stub for the WSDL defined in Issue 8 may look the following:   [WebServiceBinding(Name=”CalculatorSoap”, Namespace=”uri.test.com”)] public…

5