http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660@uzivatel > the only thing I got from this is the vocabulary Pretty much that's what you were to get from this. > separating HW from SW plus telling each component what it is, a DB running? IIS? linux? where's cache? Those are implementation details. For now I believe Ayende is establishing a way of describing the the entire system from a 30,000 foot view. Whether these services and components run on different physical boxes or all on the same box is for the most part is not relevant at this stage. The important things to note from here is that the system will be made up of a set of distinct services that run as separate processes. They will communicate via some form of TCP/IP protocol. The centralized services may be REST or SOAP webservices. Say, as an example that I'm making up, the "customer" uses an Active Directory Service or LDAP server to store its user info. Ayenda may interface to that using a web service for authentication so that if the "customer" later changes how they do network authentication, only that webservice would need to be updated to use the new auth service. As for the distributed services you may want to look up some of Greg Young's presentation videos on the InfoQ site and watch them for a better understanding of what I think Ayende is describing here. He has not stated yet that these services will be message based or that he will be using Command Query Seperation. Once again those are details that would still require diving too deep into the problem domain at this point. First I suspect he will return to the auth spec from the previous post and describe how he plans on breaking up the authentication context and where each of those parts will be handled using the above component and service types. Disclamer: The above is my interpretation and in no way should be taken as coming from Oren. I'm not Oren and do not share his ability to intimidate both code and people with my sheer physical size :-) http://ayende.com/4091/macto-defining-centralized-service-distributed-service-and-localized-component#comment3http://ayende.com/4091/macto-defining-centralized-service-distributed-service-and-localized-component#comment3Thu, 30 Jul 2009 17:43:41 GMTUz, I think you might be trying to gleen too much from this post. All he is really doing is defining some terminology that he'll be using in future posts. I'm sure there'll be posts galore explaining where the DB, Cache, et al will be located. http://ayende.com/4091/macto-defining-centralized-service-distributed-service-and-localized-component#comment2http://ayende.com/4091/macto-defining-centralized-service-distributed-service-and-localized-component#comment2Thu, 30 Jul 2009 17:42:21 GMTam I the only one that didn't get it? well, a picture would be definitely helpful as being more verbose in some parts (e.g. separating HW from SW plus telling each component what it is, a DB running? IIS? linux? where's cache? ) I am completely lost, the only thing I got from this is the vocabulary :), service, component and distributed. well...hope I will be able to follow your posts oren http://ayende.com/4091/macto-defining-centralized-service-distributed-service-and-localized-component#comment1http://ayende.com/4091/macto-defining-centralized-service-distributed-service-and-localized-component#comment1Thu, 30 Jul 2009 15:52:22 GMT