Designing a Microsoft SharePoint 2010 Infrastructure Vol 1 part 12 potx

MCT USE ONLY. STUDENT USE PROHIBITED
Planning a Service Application Architecture 2-31
Lesson 3
Topologies for Service Applications

The flexibility of the service application architecture means that there is no single
correct solution for all SharePoint 2010 environments. You must review the
business requirements, IT drivers, and governance directives to identify the best
solution for your organization.
You must understand the available options and their benefits and disadvantages
before you plan your service application architecture. One of the advantages of the
architecture in SharePoint 2010 is its flexibility, so you can modify your
deployment if your business requirements change.
Objectives
After completing this lesson, you will be able to:
• Describe the impact of service applications on solution design.
• Describe the advantages and disadvantages of designing service applications in
a single proxy group.
MCT USE ONLY. STUDENT USE PROHIBITED
2-32 Designing a Microsoft® SharePoint® 2010 Infrastructure
• Describe the advantages and disadvantages of designing multiple service
application proxy groups in multiple application pools.
• Describe the advantages and disadvantages of deploying multiple service
application proxy groups in a single application pool.
• Describe the advantages and disadvantages of an enterprise service farm
topology and cross-farm sharing of service applications.


MCT USE ONLY. STUDENT USE PROHIBITED
Planning a Service Application Architecture 2-33
Effect of Service Applications on Topology Design

Key Points
Service applications can have a major impact on the topology of your overall
solution. This is because users want functions and service applications offer a wide
range of functionality. The breadth of these service offerings means that you can
chose from a wide range of implementation topologies. The flexibility of the service
application architecture enables you to create many alternative designs. It is
important that you ensure that your design is functional rather than unnecessarily
complex. Key elements to remember when you select your topology design
include:
• Granular topologies. Most important is that you use the granularity of the
service application architecture to ensure that you can deliver the business
requirements across the organization without wasting resources, such as
administrative time or hardware budget.
• Extensible topologies. Remember that you can now extend your service
architecture. This does not just mean that you can add service applications or
extend across farms or domains. You can increase performance or capacity by
MCT USE ONLY. STUDENT USE PROHIBITED
2-34 Designing a Microsoft® SharePoint® 2010 Infrastructure
adding service instances to deal with growth. This may also be an option for
managing spikes in demand or unexpected changes in usage.
• Service-driven topologies. There is also the option for developing a service
application–driven topology. This may sound unlikely, but search is a service
application and it is common for organizations to set up search-specific farms.
You may choose to extend this beyond a specific service and include a range of
services. The key point is the service application flexibility, which should
encourage you to design a solution that will fit your business.


MCT USE ONLY. STUDENT USE PROHIBITED

Planning a Service Application Architecture 2-35
Topology for a Single Farm with a Single Service
Application Proxy Group

Key Points
The slide shows a relatively simple topology. All of the service applications are in a
single Default service application proxy group. All sites have access to all of the
farm service applications.
This may seem a very simple approach, but simplicity is often the most elegant
solution. This option is easy to deploy and manage because much of the
configuration capitalizes on the default settings. The design offers centralized
maintenance with minimal effort, and it is unlikely that users will have issues when
they access service applications.
If there is an issue regarding this topology, it is scalability. There is no separation of
services dependent on the requirements of unique areas of the business. There is
also no option for individual departments to manage their own service
applications. Therefore, if the volume of business increases, the load on the central
IT team may also increase.
MCT USE ONLY. STUDENT USE PROHIBITED
2-36 Designing a Microsoft® SharePoint® 2010 Infrastructure
This is almost certainly the most common deployment topology for service
applications, although part of that may be to do with the fact that it works for the
majority of new installations. If this is the solution that you choose, you should
review it as part of your ongoing review process to determine whether your
organization may gain benefits from other deployment options for service
applications.

MCT USE ONLY. STUDENT USE PROHIBITED
Planning a Service Application Architecture 2-37
Topology for a Single Farm with Multiple Service

Application Proxy Groups in Multiple Application Pools

Key Points
The topology on the slide provides a greater element of isolation for users in Web
App 1 because it implements a custom service application proxy group. This
provides these users with a set of service application resources that are not
available to the farm users of Web App 2 and Web App 3.
This solution provides greater isolation by putting services that are dedicated to
the custom group in a separate application pool. It is important to note that you
can share service applications across both Default and custom groups. You can
also share them among Web applications.
In this topology, simplicity is sacrificed to greater granularity. This inevitably
makes management more complex, but this should not be an issue if you maintain
documentation of your solution.

MCT USE ONLY. STUDENT USE PROHIBITED
2-38 Designing a Microsoft® SharePoint® 2010 Infrastructure
There is greater isolation of services, which provides some data security. It may be
that one of the service applications in the custom group is a second instance of a
service application that is available in the Default group. Deployment of another
instance will consume additional farm resources, but this may be justified by the
increased granularity of service.

MCT USE ONLY. STUDENT USE PROHIBITED
Planning a Service Application Architecture 2-39
Topology for a Single Farm with Multiple Service
Application Proxy Groups in a Single Application Pool

Key Points
The example on this slide looks considerably more complex, but it is just an

extension of the practices that the previous examples used. In this example, the
farm has more than one custom group. This may be a requirement because several
divisions require a single service to be isolated. For example, each may use an
instance of Excel Services that they want to keep separate, perhaps maintaining
different databases to increase separation.
You can also use this type of topology to provide unique service applications to
individual Web applications, which use a delegated model to reduce pressure on
central IT resources.
Topologies that provide custom service application proxy groups are most useful
for organizations that have divisions or teams that require a degree of separation
from the rest of the business. The custom group may also be useful for specialist
sites where separation is essential, such as sites that provide access to external
partners or customers.
MCT USE ONLY. STUDENT USE PROHIBITED
2-40 Designing a Microsoft® SharePoint® 2010 Infrastructure
Topology for Enterprise Service Farms

Key Points
Enterprise organizations are not always more complex than other environments.
However, they are usually much larger, so there is greater scope for more unique
requirements and pressing solution boundaries. Remember that if you work for a
large enterprise, it does not mean that you must design a complex solution.
In the scenario on the slide, there are a number of different approaches to service
application deployment.
Enterprise Services Farm
You can use an Enterprise Services Farm to share service applications. This enables
the central IT department to provision all shareable services across the
organization, such as corporate taxonomies through the Managed Metadata
Service. This topology is also attractive for pan-organization Search Service
implementations.