There is imho nothing wrong with WCF ria services. If you have a service layer you can still create a seperate layer ready to be consumed by your silverlight apps, your logic is still in the service layer and you are not directly working with the entities but with the dto’s so from within this perspective WCF ria services is actually very useful.

RavenDB is nice for those 0.05% of applications that would really benefit from it because admit it, the only reason to use it is for an increased performance and in my 12 year career that has never been an issue for almost all typical line of business and point of sale applications especially comparing the cost of hardware with the cost of development.

public virtual bool Equals(TValueObject other)
{
if (ReferenceEquals(null, other)) return false;
return ReferenceEquals(this, other) || BuildStructuralIdentity().Equals(other.BuildStructuralIdentity());
}

protected abstract object BuildStructuralIdentity();

public override bool Equals(object obj)
{
return Equals(obj as TValueObject);
}

public override int GetHashCode()
{
return BuildStructuralIdentity().GetHashCode();
}

And using:
public class Address : ValueObject
{
private readonly string street;
private readonly uint house;

public Address(string street, uint house)
{
this.street = street;
this.house = house;
}

protected override object BuildStructuralIdentity()
{
return new {street, house};
}
}
There is no overhead with threads and the developer will never forget about it.

and “No Coca-Cola today” refers to a open source jihad follower who was very upset the last time miguel de icaza was mentioning microsoft products @ fosdem (2006 or so) and started comparing the products miguel was introducing with coca cola, apparently his english skills weren’t that good and “coca cola” was kinda the only word he was yelling all the time.