• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
 

Sharepoint 2010: Practical Architecture from the Field

on

  • 2,596 views

Presentation from Microsoft Days 2011 (Sofia, Bulgaria). It covers the main topics during Sharepoint 2010 Architecture planning process as well as some pain points from the field.

Presentation from Microsoft Days 2011 (Sofia, Bulgaria). It covers the main topics during Sharepoint 2010 Architecture planning process as well as some pain points from the field.

Statistics

Views

Total Views
2,596
Views on SlideShare
1,677
Embed Views
919

Actions

Likes
1
Downloads
14
Comments
0

25 Embeds 919

http://tihomirignatov.blogspot.com 761
http://tihomirignatov.blogspot.in 42
http://tihomirignatov.blogspot.co.uk 21
http://tihomirignatov.blogspot.de 20
http://tihomirignatov.blogspot.ca 15
http://tihomirignatov.blogspot.com.au 11
http://tihomirignatov.blogspot.fr 6
http://tihomirignatov.blogspot.it 5
http://tihomirignatov.blogspot.se 5
http://tihomirignatov.blogspot.com.es 4
http://feeds.feedburner.com 4
http://tihomirignatov.blogspot.nl 3
http://tihomirignatov.blogspot.kr 3
http://tihomirignatov.blogspot.com.br 3
http://tihomirignatov.blogspot.mx 2
http://tihomirignatov.blogspot.tw 2
http://tihomirignatov.blogspot.sg 2
http://tihomirignatov.blogspot.co.at 2
http://tihomirignatov.blogspot.ch 2
http://tihomirignatov.blogspot.pt 1
http://tihomirignatov.blogspot.ie 1
http://tihomirignatov.blogspot.no 1
http://translate.googleusercontent.com 1
http://tihomirignatov.blogspot.ru 1
http://tihomirignatov.blogspot.co.nz 1
More...

Accessibility

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Boundaries are absolute limits that cannot be exceeded by design. It is important to understand these limits to ensure that you do not make incorrect assumptions when you design your farm.An example of a boundary is the 2 GB document size limit; you cannot configure SharePoint Server to store documents that are larger than 2 GB. This is a built-in absolute value, and cannot be exceeded by design. Thresholds are those that have a default value that cannot be exceeded unless the value is modified. Thresholds can, in certain circumstances, be exceeded to accommodate variances in your farm design, but it is important to understand that doing so may impact the performance of the farm as well as the effective value of other limits.The default value of certain thresholds can only be exceeded up to an absolute maximum value. A good example is the document size limit. By default, the document size limit is set to 50MB, but can be changed to a maximum value of 2 GB. Supported limits define the tested value for a given parameter. The default values for these limits were defined by testing, and represent the known limitations of the product. Exceeding supported limits may cause unexpected results, significant performance degradation, or other detrimental effects. Some supported limits are configurable parameters that are set by default to the recommended value, while others relate to parameters that are not represented by a configurable value.An example of a supported limit is the number of site collections per Web application. The supported limit is 500,000, which is the largest number of site collections per Web application that met performance benchmarks during testing. It is important to note that many of the limit values provided in this document represent a point in a curve that describes an increasing resource load and concomitant performance degradation as the value increases. Therefore, exceeding certain limits, such as the number of site collections per Web application, may only result in a fractional decrease in farm performance. However, in most cases, operating at or near an established limit is not a best practice, as acceptable performance and reliability targets are best achieved when a farm’s design provides for a reasonable balance of limits values.Thresholds and supported limits guidelines are determined by performance. In other words, you can exceed the default values of the limits, but as you increase the limit value, farm performance and the effective value of other limits may be affected. Many limits in SharePoint Server can be changed, but it is important to understand how changing a given limit affects other parts of the farm.
  • http://technet.microsoft.com/en-us/library/cc748824.aspx
  • http://technet.microsoft.com/en-us/library/gg441256.aspxhttp://technet.microsoft.com/en-us/library/dd755969(WS.10).aspx

Sharepoint 2010: Practical Architecture from the Field Sharepoint 2010: Practical Architecture from the Field Presentation Transcript

  • Sharepoint 2010: Practical Architecture from the Field
    Tihomir Ignatov
    Senior Consultant
    Microsoft Corporation
  • Session Objective(s):
    Recognize the importance of having a detailed understanding of the different SharePoint deployment models and options
    Understand the implications of the different options, and the ramifications and consequences of each
    Focus on choosing the appropriate option for our customers based on their business and technical requirements
    Take away(s):
    Truly successful architecture design for SharePoint requires both broad and deep technology skills, essentially requiring an understanding of both IT Pro and Development aspects
    Session Objectives and Takeaways
  • Architecture in Sharepoint Deployments
    Deployment Architecture
    Network Architecture
    Enterprise architecture
    Server architecture
    Permission architecture
    Cloud architecture
    Infrastructure architecture
    Deployment Architecture
    Software Architecture
    Data architecture
    Information architecture
    Business architecture
  • To build application that satisfies the business and IT requirements
    Choosing appropriate technical solution based on the requirement and the maturity of the team involved
    Sharepoint Architecture – What is it for?
  • Architecture is Making ideas real
    “Make everything as simple as possible, but not simpler.”
    -Albert Einstein
  • Best practices vs. real world
    Supportability!
    Sharepoint 2010 boundaries and limits
    Performance
    Capacity (plan and maintain)
    Client Machines
    High Availability and Scalability
    Network Infrastructure
    Deployment of customizations
    Support and Maintenance
    What to consider?
  • Always use best practices (BP) when is possible
    Adapt your design to the business requirements
    Do not hesitate to jump over the BP if is reasonable, but leave a track why (document it)
    Always weigh out the business requirements against feature TCO (complexity, time, resources, price, etc.)
    Say “NO” to your client, when the feature is expensive and low business impact
    Best Practices vs. Real World
  • Supportability
    Use only SUPPORTED scenarios for customization and configuration
    Do not use Quick & Dirty approach for production
    What is supported?
    Ask for supportability!
  • Boundaries are absolute limits that cannot be exceeded by design.
    Thresholds are those that have a default value that cannot be exceeded unless the value is modified.
    Supported limits define the tested value for a given parameter.
    Limits
    Thresholds and supported limits guidelines are determined by performance.
  • Some Important Limits
    Software boundaries and limits at TechNet
  • Capacity is directly affected by scalability
    If your solution plans exceed the recommended guidelines
    Evaluate the solution to ensure that compensations are made in other areas.
    Flag these areas for testing and monitoring as you build your deployment.
    Redesign or partition the solution to ensure that you do not exceed capacity guidelines.
    Take Into Account…
  • How to design the solution (Sub Sites vs. Site Collections vs. Web Applications)
    Which SA to provision
    Do not use the Farm Configuration Wizard
    Important Decisions
  • “Some” resources in Technet…
    Consider the limits!
    Storage and SQL capacity planning
    For content databases
    For Service Applications
    Always test storage performance with SQLIO tool
    Make meetings with storage administrators 
    Capacity Planning
    My capacity planning tool: http://tihomirignatov.blogspot.com/2010/12/sharepoint-2010-capacity-planning-and.html
  • Browser and version
    MS Office version
    Client PCs – HW & SW configuration, load, other applications
    Monitor and test page rendering performance on regular PC (not development)
    Client Compatibilities
  • Is the Sharepoint a business critical application?
    Try to define SLA and down time – cost, operations, reliability
    From scalability and capacity to availability
    Database availability strategies – clustering or mirroring?
    Service Applications redundancy strategies
    SA that store data outside a database
    SA that store data in databases
    Search Service Application redundancy
    High Availability
  • Scale up or scale out?
    When to scale?
    What to scale?
    Scalability
  • Understand the connectivity between Data center and branches
    Mobile views
    Office Web Apps
    Office 2010 Document Cache and the MS-FSSHTTP protocol
    Outlook 2010
    Sharepoint Workspace 2010
    BranchCache with Windows 7 and Windows Server 2008 R2
    The connectivity
  • Consider OOB Backup/Restore tools
    SQL backup for content
    MS DPM 2010 and 3rd party tools
    Disaster Recovery scenarios
    Backup and Recovery
  • Customizations and content
    Sharepoint deployment framework
    Logging and monitoring
    Exception handling
    Development
    • SharePoint designer increases flexibility, but if misused, can have direct impact on versioning model
    Hybrid models
    SPD allowed for site customizations, but not for page layouts or master pages
    SPD allowed for team sites, but not in corporate communicational intranet
    To SPD or not SPD?
  • What is this?
    MS Online considerations
    BPOS-D – limitations and releases
    Office 365 SharePoint deployment is in single site collection (sandbox)
    Sharepoint Online
  • It’s all about governance
    Define the development process
    Define the quality assurance process in the individual project and in the full deployment
    Define the ground rules of the deployment
    Define the models to administer and manage the deployment
    Application Life Cycle Management (ALM)
    Software Development Life Cycle (SDLC)
    Software Quality Lifecycle
    Business Continuity Management (BCM)
    Portal Life Cycle Management
    Not just ALM or BCM, it’s the entire process for the lifecycle of the deployment...
  • My blog: http://tihomirignatovblogspot.com
    Sharepoint User Group Bulgaria: http://www.sugbg.org
    E-mail: contact@sugbg.org
    Contact me
  • Q & A