lync 2013 contains below roles

As per my knowledge lync 2013 contains below roles.

•      Front End Server and Back End Server
•      Edge Server
•      Mediation Server
•      Director
•      Persistent Chat

but can some one please help me by telling in simple words what these roles do, simple words will be appreciable links not required.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Steven SheeleyConsulting SW Engineer - Lync/Skype4BusinessCommented:
Standard Edition Server
The Standard Edition server is designed for small organizations, and for pilot projects of large organizations. It enables many of the features of Lync Server, including the necessary databases, to run on a single server. This enables you to have Lync Server functionality for a lower cost, but does not provide a true high-availability solution.
Standard Edition server enables you to use instant messaging (IM), presence, conferencing, and Enterprise Voice, all running on one server.
For a high-availability solution, use Lync Server Enterprise Edition.

Front End Server and Back End Server
In Lync Server Enterprise Edition, the Front End Server is the core server role, and runs many basic Lync Server functions. The Front End Server, along with the Back End Servers, are the only server roles required to be in any Lync Server Enterprise Edition deployment.
A Front End pool is a set of Front End Servers, configured identically, that work together to provide services for a common group of users. A pool of multiple servers running the same role provides scalability and failover capability.
The Front End Server includes the following:
    User authentication and registration
    Presence information and contact card exchange
    Address book services and distribution list expansion
    IM functionality, including multiparty IM conferences
    Web conferencing, PSTN Dial-in conferencing and A/V conferencing (if deployed)
    Application hosting, for both applications included with Lync Server (for example, Conferencing Attendant and Response Group application), and third-party applications
   Optionally, Monitoring, to collect usage information in the form of call detail records (CDRs) and call error records (CERs). This information provides metrics about the quality of the media (audio and video) traversing your network for both Enterprise Voice calls and A/V conferences.
    Web components to supported web-based tasks such as web scheduler and join launcher.
    Optionally, Archiving, to archive IM communications and meeting content for compliance reasons. In Lync Server 2010 and prior versions, Monitoring and Archiving were separate server roles, not collocated on Front End Server.
    Optionally, if Persistent chat is enabled, Persistent Chat Web Services for Chat Room Management and Persistent Chat Web Services for File Upload/Download.

Front End Pools are also the primary store for user and conference data. Information about each user is replicated among three Front End Servers in the pool, and backed up on the Back End Servers.
Additionally, one Front End pool in the deployment also runs the Central Management Server, which manages and deploys basic configuration data to all servers running Lync Server. The Central Management Server also provides Lync Server Management Shell and file transfer capabilities.
The Back End Servers are database servers running Microsoft SQL Server that provide the database services for the Front End pool. The Back End Servers serve as backup stores for the pool’s user and conference data, and are the primary stores for other databases such as the Response Group database. You can have a single Back End Server, but a solution that uses SQL Server mirroring is recommended for failover. Back End Servers do not run any Lync Server software.
We do not recommend collocating Lync Server databases with other databases. If you do so, availability and performance may be affected.
Information stored in the Back End Server databases includes presence information, users' Contacts lists, conferencing data, including persistent data about the state of all current conferences, and conference scheduling data.

Edge Server
Edge Server enables your users to communicate and collaborate with users outside the organization’s firewalls. These external users can include the organization’s own users who are currently working offsite, users from federated partner organizations, and outside users who have been invited to join conferences hosted on your Lync Server deployment. Edge Server also enables connectivity to public IM connectivity services, including Windows Live, AOL, Yahoo!, and Google Talk. Deploying Edge Server also enables mobility services, which supports Lync functionality on mobile devices. Users can use supported Apple iOS, Android, Windows Phone, or Nokia mobile devices to perform activities such as sending and receiving instant messages, viewing contacts, and viewing presence. In addition, mobile devices support some Enterprise Voice features, such as click to join a conference, Call via Work, single number reach, voice mail, and missed calls. The mobility feature also supports push notifications for mobile devices that do not support applications running in the background. A push notification is a notification that is sent to a mobile device about an event that occurs while a mobile application is inactive. Edge Servers also include a fully-integrated Extensible Messaging and Presence Protocol (XMPP) proxy, with an XMPP gateway included on Front End Servers. You can configure these XMPP components to enable your Lync Server 2013 users to add contacts from XMPP-based partners (such as Google Talk) for instant messaging and presence.

Mediation Server
Mediation Server is a necessary component for implementing Enterprise Voice and dial-in conferencing. Mediation Server translates signaling, and, in some configurations, media between your internal Lync Server infrastructure and a public switched telephone network (PSTN) gateway, IP-PBX, or a Session Initiation Protocol (SIP) trunk. You can run Mediation Server collocated on the same server as Front End Server, or separated into a stand-alone Mediation Server pool.

Directors can authenticate Lync Server user requests, but they do not home user accounts or provide presence or conferencing services. Directors are most useful to enhance security in deployments that enable external user access. The Director can authenticate requests before sending them on to internal servers. In the case of a denial-of-service attack, the attack ends with the Director and does not reach the Front End servers.

Persistent Chat Server Roles
Persistent chat enables users to participate in multiparty, topic-based conversations that persist over time. The Persistent Chat Front End Server runs the persistent chat service. The Persistent Chat Back End Server stores the chat history data, and information about categories and chat rooms. The optional Persistent Chat Compliance Back End Server can store the chat content and compliance events for the purpose of compliance.
Servers running Lync Server Standard Edition can also run Persistent chat collocated on the same server. You cannot collocate the Persistent Chat Front End Server with Enterprise Edition Front End Server.
Front End Server basically is a server, or set of servers (front end pool) with the same config, that runs most all of the Lync server functions. At least one of your Front Ends will need to have the Central Management Server loaded on it. Considered the core role, it is required. Some items it does specifically are authentication, address book services, presence info, IM, App hosting, and Web conferencing.

Edge Server is an optional role that allows you to collaborate using Lync outside of your firewall. This role would host your web conferencing sessions with invited people outside of your organization, allow IM to the outside, presence, etc.

Back End Server(s) contain the SQL databases the store most of the data. Items such as contacts, presence info, conferencing and scheduling data are stored here. The back end also serves as backup stores for the pool’s user and conference data, and are the primary stores for other databases. It is best to have some sort of of SQL server mirroring is recommended for redundancy here. Back End is a required role.

Mediation Server is for Voice and Dial In conferencing. Only needed if you plan to use Telephony features with Lync.

The Director role is basically a login firewall for outside users you have granted resource access. It does the authenticating before sending to the servers. This way anything with bad intentions (such as a denial of service attack) gets dumped on the Director server and not on your critical Lync servers. This role should be on it's own server.

Persistent Chat Server Role is an optional role that allows users participate in message board style chat. Usually topic based, like on a message board, and can be configured to sort topics as you like (usually by latest comment). This roles keeps the chat history so you should have plenty of log space for this role.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Exchange_DonAuthor Commented:
thanks @ tshearon for your nice explaination, just last one thing as you told the Director role is basically a login firewall for outside users you have granted resource access.

so this server has to be in DMZ or it has to be part of domain?
Steven SheeleyConsulting SW Engineer - Lync/Skype4BusinessCommented:
Directors are located inside the domain. Only edge servers are in the DMZ.
The Director's role is deployed internally. It does a lot more than what I scratched the surface on.

From the article I am including:

"If you're deploying Edge Servers, you can deploy a Director to authenticate external users and then proxy their traffic to internal servers. When you use a Director in this manner, it relieves the Front End pool servers from the overhead of performing authentication of these users. It also helps insulate internal Front End pools from malicious traffic such as Denial of Service (DoS) attacks."

"If you deploy multiple Front End pools at a central site, you can improve performance on the Front End servers by adding a Director to that site, which alleviates the need for them to fulfill the redirect requests from clients. In this scenario, all requests go first to the Director, which then routes them to the correct Front End pool."

If you would like more detail here is the article.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.