What is the best architecture for content-oriented website/portal?
A:
CouchDB would be interesting to look at for this project.
What CouchDB is
•A document database server, accessible via a RESTful JSON API.
•Ad-hoc and schema-free with a flat address space.
•Distributed, featuring robust, incremental replication with bi-directional conflict detection and management.
•Query-able and index-able, featuring a table oriented reporting engine that uses Javascript as a query language.
What it is Not
•A relational database.
•A replacement for relational databases.
•An object-oriented database. Or more specifically, meant to function as a seamless persistence layer for an OO programming language.
Even Mien
2009-08-01 20:45:10
+4
A:
The best architecture for a content-oriented portal consists of one or more web servers, one or more database servers, and a permanent internet connection. You'll also need some code to run the portal.
Past that point, everything depends on the specifics of your project. And honestly, even if you listed all the specifics of your project, it would still be a highly subjective question that would have no definitively correct answer.
zombat
2009-08-01 21:07:19
A:
@zombat has the correct answer, and my vote.
But, if you're looking for some basic suggestions to help you along, I would suggest looking at Drupal, Mambo, Joomla, and Django. It may turn out that none of them are appropriate for what you're doing, but they all provide good examples (in their own, different ways) of how it should be done.
anschauung
2009-08-02 03:42:16
A:
The serving of the content is not too difficult, providing resilience by using several servers clustered in some way is also a reasonably understood problem. I see the real chanllenge as being the management of the content. Allowing non-technical authors to get material into this system and to maintain it.
I would be reluctant to develop all of that from scratch. There are plenty of commerical products and open source solutions such as Drupal.
djna
2009-08-03 07:26:56