Make Sitecore

Architecture
More Powerful

http://www.itorigins.com
www.itorigins.com

ITOrigins is Best sitecore

cms online training institute in
hyderbad .
ITOrigins offering
1.Top Class training
2.Industry Recognized Certification
3.Dedicated to Placement Assistance

http://www.itorigins.com
 How to make
Sitecore architecture
more powerful!
Sharing some tips and best pratices
for robost sitecore architecture

http://www.itorigins.com
 “Architecture begins where
engineering ends. - Walter
Gropius”

“Architecture is as important in
software development as it is in
building construction. No one
breaks ground on a building
without any plans and good
architect”

http://www.itorigins.com
 The architect should be very
careful about Sitecore IA
architecture and initial back
grounding of the project.

He/she should know all the

alternative and pros/cons of the
technology and of course cost.

http://www.itorigins.com
24 Points
That every Sitecore
Architect Should Know:
With the non-functional requirements captured, the next step
is to start thinking about how you're going to solve the
problems set out by the stakeholders and define the
architecture.

http://www.itorigins.com
1: Identify the scope of the
project
scope of the project must decide at the
very begging of the any project so
accordingly we can design/architect the
application, below are some few sample
questions that needs to be asked for a
customer for Sitecore applicable

http://www.itorigins.com
› Identify the scope of theproject:
› How will the website use thecontent?
› Scope of data migration?
› Scope of Web Forms?
› Scope of any third party integration like CRM, Sales-
force, Facebook
› Infrastructure requirement would be on cloudor
physical servers?
› Any specific performance required?
› Any rapid development requires like campaign etc.
› Scope of multi-lingual and multi-site?
› Scope of DMS, what type of reporting they want?
› What kinds of content itemsexist?

http://www.itorigins.com
› What types of content elements will appear
consistently on multiple pages (also known as
reusable content)?
› Where does the aforementioned, reusable content
come from?
› Does the reusable content display different content
on different pages?
› Does the system display content from other systems?
› How do you integrate the content from the other
systems?
› Is the solution multilingual? If so, does the contenton
the multilingual versions differ?
› What kinds of users will have access to the CMS?
› What website regions or content types will each user
have access to?

http://www.itorigins.com
2: Choose the Right Sitecore
version:
Always choose the right version of Sitecore, before
project getting started. It’s not always good to
implement the latest version of Sitecore, it should
be decided after considering the factors below

1. Team strength
2. Product version maturity and stability
3. Cost
4. Scope and timeline of the Project.

http://www.itorigins.com
3: Selection of technology:

Web Forms and MVC are two different approachesfor

building Sitecore application

Both can be excellent choices, and both can be very bad

choices,

Depending the requirements of theapplication and the

knowledge and experience of the team on technology.

http://www.itorigins.com
4: Setup Sitecore project and
code deployment methodology
There are two ways to set up the visual studio solution
with Sitecore. Your solution is fully coupled with the
Sitecore web site.

http://www.itorigins.com
5: Identify the build deployment
process:
Architect need to be decided which methodology
should be used for deployment purpose, obviously the
cost can be the most important factor like TDS has
license cost over serialization or package creation
methodologies.

http://www.itorigins.com
6: Use of Sitecore Rocks:
its need to be decided that Sitecore rock would be used
in the project or not. Sitecore itself recommends using
this tool for rapid development.
Best sitecore cms online training will gives you
command over the sitecore

http://www.itorigins.com
7: Responsive design framework
RWD is very common now’s a day, it need to be decided
which framework would use for responsive design like
bootstrap, htm5 etc. So, accordingly resource and design
would be finalized.

http://www.itorigins.com
8: Third party integration
It should be proper planning for any third party
integration with Sitecore application like CRM, Sales
force, etc., so, accordingly IA architecture and solution
can be designed.

http://www.itorigins.com
9: Defining IA
Information architecture design can be as significant as
the coding of a CMS solution. Below are some important
aspect that should be considered

http://www.itorigins.com
10: Scope of DMS
Sitecore layout, template, DB design (Mongo-DB in
Sitecore 7.5 or later) must be designed based on the
DMS scope like personalization, email campaigning etc.

http://www.itorigins.com
11:Search selection
search is the backbone of any ECM system, so need to
decide very carefully which search pattern or framework
should be implemented like Lucence, Solr, Coveo,
custom search pattern.

http://www.itorigins.com
12: Setting multiple site solution
It is possible to have multiple sites in the same solution
in Sitecore, but there are a few pitfalls and issues which
need to be taken care while developing the solution.

http://www.itorigins.com
13: Identify the multi-lingual
solution
Architect also needs to consider the factor of multi-
lingual solution while creating an IA including template,
layouts, presentation and standard value.

http://www.itorigins.com
14: Publishing architecture
publishing is very time consuming process in Sitecore
application, sometime we required the dedicated
Sitecore instance for publishing task to avoid long
queue.
So here we need to decide and set up the accordingly

http://www.itorigins.com
15: Setup multiple CM andCD:
By default, each Sitecore instance provides both content
management (CM, for CMS users maintains the managed
sites) and content delivery (CD, for visitors to those
managed sites). But we can separate the CM and CD
facilities into separate environments, typically involving
separate servers. It’s always recommended to keep
separate the CM and CD environment. Below are some
advantage of separating CM and CD:
· Scalability
· Performance
· Security
· Administrationhttp://www.itorigins.com
16: Handling media library:
we can manage a media library within Sitecore by two
ways either in
Database or file system. Both have pros and cons so, at
the time of designing the project we need to decide the
best approach. Also, we need to consider some cloud
based approaches like DAM with Sitecoreetc.

http://www.itorigins.com
17: Cachingimplementation
Cache plays very important role in website performance.
So, an understanding of all Sitecore caches is really
important before implemented. If we understand all of
them, then it would be easy to do performance tuning
using cache settings.

http://www.itorigins.com
18: Web form implementation
Architect also needs to identify the web form marketer
scope and find out how it compatible with MVC.

http://www.itorigins.com
19: Logging mechanism
Sitecore uses log4net for its logging purposes, but in
some situations we need to build a custom logging
mechanism. One of the most common scenarios would
be a multi-site solution in which the standard log will
become huge and finding the exact trace information
becomes painful. so we need to consider this factor at
the time of designing the architecture of the application.

http://www.itorigins.com
20: Error handling in Sitecore
we need to consider various levels of exception/error
handling like Custom Errors, Try... Catch... Finally Blocks,
XSL Exception Management, Web Forms Exception
Management, MVC Exception Management, Application
(Global) Exception Management, Error Pages, Managing
Exceptions. So after taking all error handling, need to
decide the base architecture where it should be
forcefully implemented..

http://www.itorigins.com
21: Sitecorecustomization
Architect needs to identify the scope of customization
in Sitecore like pipeline and some UI customization so
accordingly template and project should be modified
from the very beginning of the project.

http://www.itorigins.com
22: Consider Sitecore
performance
Sitecore IA plays a very important role in performance
point of view, below are some points that need to be
considered for optimization purpose of the application:

· Avoid Item which has more than 100items.

· Caching tuning
· Enable CSS, JSCaching, Compression
· IA architecture (avoid creating items with
hundreds of children
· Optimization in publishing wizard
· Prevent use of Get Descendants
· IIS level optimization
http://www.itorigins.com
23: Sitecore security
Sitecore provides a comprehensive security
infrastructure that you can use to secure any item in any
Sitecore database. An architect should know all the
aspect of Sitecore security and should implement atthe
time of designing the application. Sitecore alsoprovides
additional functionality that enables you to use
Microsoft Dynamics Customer Relationship
Management (CRM) and Active Directory (AD) for
authentication.

http://www.itorigins.com
Below are the some security topics that need to be
considered at the time of designing the site.
· Access rights
· Users
· User profile
· Roles (groups)
· Domains
· Security inheritance
For more information:

http://www.itorigins.com/sitecoreonlinetraining.aspx

http://www.itorigins.com
24: Scope of data migration
Scope of data migration requirement should behandled
from beginning of the project here you can find the
complete details on this topic.

http://www.itorigins.com/sitecoreonlinetraining.aspx

http://www.itorigins.com