Click here to Skip to main content
15,896,497 members
Please Sign up or sign in to vote.
1.00/5 (2 votes)
See more: (untagged)
Whats the difference between repository and client-server architecture?
In both systems, there is a shared database that can be accessed by subsystems. I can't figure the real difference because client-server does what the repository system does.
Posted
Comments
Sergey Alexandrovich Kryukov 14-Nov-13 14:50pm    
This is the same as asking: "what's the difference between Ford and highway?" :-)
Avoid "difference" questions, they are rarely can be correct.
—SA

Go through Article- Software Architectural Analysis(Layered, Repository, Client-Server)[^].
Quote:
Repository Architecture

A repository architecture is a system that will allow several interfacing components to share the same data. Each component interfaces the same dataset that is utilized system wide. Data manipulation taking place in one component will reflect an identical representation of data in another component. Components can be interchanged and are independent of other system components. A good example of a repository architecture would be a database management system. Such a system would provide both a console and graphical user interface to update both the structure and dataset of any particular database.

Client-Server Architecture

A client-server architecture is a system that provides distinct services to multiple clients by logically dividing the service providers. Each service may be hosted on another server although the services can be co-located all on one server. Several clients may run concurrent instances of any given service simultaneously. One server can be replaced or undergo maintenance without affecting the entire system. A great advantage of client-server architecture is that is a distributed architecture providing the possibility of integrating geologically separated components all into one system. A good example of a client-server architecture is a library system that may provide multiple services to multiple students such as an article database, a book finder and an order placer.
 
Share this answer
 
Comments
José Amílcar Casimiro 14-Nov-13 12:17pm    
Repository Architecture in the given article is a design pattern in my point of view. Why do you call it an architecture? Thanks.
Sergey Alexandrovich Kryukov 14-Nov-13 14:57pm    
I voted 5. Please see my comment to your solution and my comment to the question.
If you want to reply to gibberish, you can reply in any reasonable way, not expecting appreciation... :-)
—SA
José Amílcar Casimiro 14-Nov-13 15:54pm    
maybe there is some argument that shows that I am wrong. I am humble enough to say that I do not know everything. I always learn new things.

JAFC
Sergey Alexandrovich Kryukov 14-Nov-13 16:07pm    
Sure. I think, you did not say anything wrong, in terms of technology. I would suggest not to take poor questions too seriously. And, in many cases, it's good not to answer.
Even if the answers by Tadish and yours one was not there, I would probably left only a comment.
—SA
José Amílcar Casimiro 14-Nov-13 16:30pm    
:)
Hello,

Client-Server Architecture - http://technet.microsoft.com/en-us/library/cc917543.aspx[^]

The repository does not make sense to me, because it is not an architectural model. There is nothing to compare.

JAFC
 
Share this answer
 
v4
Comments
Sergey Alexandrovich Kryukov 14-Nov-13 14:56pm    
I voted 4. Who told you that you need to answer about "architectural model". OP does not understand architectural models, and the question is gibberish, anyway. Please see my comment to the question.
If you want to reply to gibberish, you can reply in any reasonable way, but I would say, posting just a comment and directing to RTFM is the best way.
Any possible answer to a totally incorrect question could be considered as defective. It's more important to point out OP that this is not a right way to learn anything.
—SA

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900