1-888-365-2779
+1-888-365-2779
Try Now
More in this section

Forums / Developing with Sitefinity / Expert recommendation for big scenario

Expert recommendation for big scenario

2 posts, 1 answered
  1. Hector Sustaita
    Hector Sustaita avatar
    11 posts
    Registered:
    12 May 2010
    08 Jul 2010
    Link to this post
    Hi,

    I'm working with a very big client and I would like to know your recommendations for this scenario:

    a. It's a hugge portal with a home page and many subsites for each product (over 80+ minisites)
    b. The deploy will be over 3 releases, example: 1st release => 25 minisites, 2nd => 25 minisites, 3rd => 30 minisites
    c. Not all minisites are complex, 60 of them only have 2 or 3 pages max
    d. The production URL must be: www.generalsite.com
    e. The product pages URL must be: www.generalsite.com/product
    f. A general header and footer must be on each page, including the home page (hub) and the products pages.
    g. There will be roles for each product, to allow the CMS final user to only modify and view certain pages.
    h. A breadcrumb must show from home to specific page: home > category > product > page > subpage
    i. Is considered to be in more languages.

    I was thinking of using only one Sitefinity project to implement this, and make use of page groups to consolidate the product pages.
    Also using a single database for the project.
    The average users for CMS are 15, and my web server and DB server are powerfull and have growing capabilities.
    Only the merge replication makes me have doubts over my desing structure, because the 3 releases.
    It is expected to have a large amount of visits to the minisites.

    So, what's the Sitefinity Team recommendation??
    The Sitefinity DB has any trouble for sites over 350+ pages??
    The CMS admin page has any bugs over so much roles or pages??
    Is there best practices??

    Thanks in advance.
  2. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    12 Sep 2017
    14 Jul 2010
    Link to this post
    Hello Hector Sustaita,

    I was thinking of using only one Sitefinity project to implement this, and make use of page groups to consolidate the product pages. Also using a single database for the project.
    The average users for CMS are 15, and my web server and DB server are powerfull and have growing capabilities.


    Sitefinity 3.x edition has been tested with over 20000 pages and there is no problem with the backend performance. For the public part of your website you might find this post useful Tips to optimize your website performance

    The backend is tested with 40 concurrent  users. If there are more than 40  concurrent  users there could be some performance impact.

    Only the merge replication makes me have doubts over my desing structure, because the 3 releases.
    It is expected to have a large amount of visits to the minisites
    .

    For replication you could use third FileReplication and DataBase Schema Comparison and Replication tools. Actually Visual Studio supports the last one out of the box. There are not tools that comes with Sitefinity that you can use. Of course it is possible to create a custom tool through the API, but this will be time consuming and you should be very familiar the API.


    The Sitefinity DB has any trouble for sites over 350+ pages??

    350 + pages are not a problem for Sitefinity. 

    The CMS admin page has any bugs over so much roles or pages??

    There are not any showstopper issues. Actually pages and users sections are very stable, because they are base components of the CMS.

    Sincerely yours,
    Ivan Dimitrov
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
    Answered
2 posts, 1 answered