Security will be a concern. By having a public site on the same farm as internal content means you are more at risk of the internal content becoming accessible externally. With separate farms, you can more easily isolate the servers.
It is possible to have separate web apps on the same farm that don't share any information, however it is also easy to accidently expose information, particularly through service applications like search. Having a dedicated farm for a public site is not cheap though, so I think the decision should be based on the risk of exposing internal data (either accidently or via hacking). If the consequence of a leak is not serious and the SharePoint admins can be trusted to configure appropriately, then go for it. Picking the right level of paranoia to have regarding security is tough. Just remember, if you don't think they are watching you, they are. Ivan From: [email protected] [mailto:[email protected]] On Behalf Of Ajay Sent: Tuesday, 16 April 2013 12:29 PM To: ozMOSS Subject: Website and intranet on same farm Hi Guys, SharePoint 2013 solution starting with website, later intranet for collaboration and subsequently BI services and possibly extranet. The web site is mostly static and has few hundred visitors each day. Intranet users will be around 500. We are thinking to have website and intranet/extranet on same server farm. Is it okay to have website and intranet on the same farm.. any pitfalls or pointers suggestions Next question As per example farm topologies in the MS topology guide http://zoom.it/AgjL#full ,, for less than 1000 users - 2 load balanced servers, which will have all the services running and database server should be fine. Concurrent users will be about 100 Do you think this is okay or is any good reason to add App Server in the mix, the website is fairly low usage and will likely remain so...
_______________________________________________ ozmoss mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
