|
MICROSOFT COLLABORATION and companion development technologies have really come a long
way over the past 20 years. Over this time, many different technologies have come and gone in
the blink of an eye. Others have built up momentum, improving with each new version, providing
valuable new features to meet the ever-increasing digital demands of the age in which we live.
One such technology that has done this brilliantly is SharePoint 2010. SharePoint is a culmination
of more than 20 years of continual research and investment by Microsoft. Each new version has
improved on the previous version, and provided a plethora of new features to incorporate into
deployments of SharePoint. With each new version of SharePoint, the knowledge required to design
successful deployments has grown astronomically.
In addition, from a design and architecture perspective, learning SharePoint 2010 is a huge undertaking
that touches so many specializations. This makes it really diffi cult for an aspiring architect to
understand what knowledge and skills are required to design solutions for SharePoint 2010. The result
has been a tendency by SharePoint specialists to learn and focus on a subset of the capabilities of
SharePoint 2010, and even then with a business adoption, design, infrastructure, developer, testing, or
governance orientation, but not on the overall SharePoint solution provided to customers.
An increased breadth of architectural knowledge and a better understanding of the medium- to
long-term impact of key design decisions are required to design successful SharePoint 2010 portal
solutions. This knowledge must be coupled with real-world case studies and solid “in the trenches”
expert experiences to help you avoid the common pitfalls faced by many SharePoint 2010 deployments.
Although there may be a number of fantastic development, infrastructure, and feature- or
capability-oriented books, no books have been dedicated purely to the core architectural issues faced
on a day-to-day basis by SharePoint design professionals and architects. As a result, the idea for this
book was born, and the long process began of collating the many years of wisdom and experiences,
as well as designing and authoring a book that would address each of the key architectural concerns.
The next sections cover who this book is for, and what this book covers. |
