Posts

Supporting global organisations through framework based digital platforms

Image
In my last couple of posts I've talked about when to choose a multi-site versus a multi-instance pattern for deploying Sitecore, and how we approach delivering Sitecore platforms using feature based modular development . In this post I'm going to take a look at the sorts of issues that arise when large global organisations start to look at rolling out digital platforms, and how some we can leverage some of the points that we've covered in the last couple of posts as a part of our approach to designing a Sitecore based digital platform architecture that addresses them. Tyrannies of global size Large organisations hosting a number of different websites are often confronted by some competing forces which lead them to ask about whether they should have multiple sites in a single or multiple Sitecore instances.  These are usually related to the following requirements which address different types of web presence for different parts of a business: We have different site...

Announcing Deloitte Digital Atlas framework for Sitecore

Deloitte Digital have been delivering enterprise digital platforms with Sitecore for over 6 years, and I think it is fair to say that we've learnt a lot during the dozens of projects we've delivered in that time. Yesterday we announced the open source release of our Deloitte Digital Atlas framework for Sitecore. Atlas is the underlying framework we use to deliver all our Sitecore implementations, providing a consistent set of tools and practices for accelerating high quality multi-site ready Sitecore platforms based on what we have learned across many years of enterprise Sitecore project delivery. Some of the features included are: "ORM" Sitecore fields mapper (including support for Experience Editor and also mapping non-Sitecore items) Extensible caching and logging frameworks integrated with Sitecore events Dynamic placeholder support Multi-site workflow and data source management We hope you find it useful, and even choose to contribute back to make i...

The power of modular development

Image
A modern digital platform doesn't just get built and then sit serving content pages for years without any changes or updates. Any system where you aren't continuously updating it to meet the needs of the business quickly becomes a legacy system, and other uncontrolled "micro-sites" will start popping up in other places (and all the FXM in the world can't make up for that!). The counterpoint to this however is that constant uncontrolled change to any system can result in a big ball of mud .  When your digital platform is a key organisational asset this might get even worse when you have multiple development teams on multiple releases or across multiple vendors all working on the system at once.  Even when delivering in a single stream using Agile principles your solution can get messy without a clear underlying architecture "skeleton" to which you can add meat. Sitecore's support for modular page composition through placeholders and modules pro...

Sitecore - multi-site or multi-instance?

Image
I have been asked by a number of different people recently about when it is appropriate to maintain a number of different websites on a single Sitecore instance, versus deploying multiple Sitecore instances (on the same or separate hardware) to keep sites separate. As is usually the case, the answer is "it depends", but there are some key conditions that can lead to a clear choice between one over the other. Single Instance In the single instance approach, there is a single installation of Sitecore that hosts all of an organisations sites. This means that there is one IIS website hosting Sitecore per server all sharing the same Sitecore configuration and content. Pros Single set of user access credentials for access to all sites If you are not using LDAP integration for login to your Sitecore instance (or using some other customisation such as federated security through something like ADFS), having a single instance lets you use the same set of Sitec...

Enterprise Sitecore xDB Security with MongoDB

Image
This will form the second part in a two-post set outlining some of what we learnt whilst implementing xDB and Mongo for a client with enterprise grade availability and security requirements which dictated that a The first post dealt with configuring Mongo and Sitecore to use a replica set for high availability. In this post I'll review some of the options for meeting security requirements around the Mongo implementation for xDB. Security For this project, we had some quite stringent privacy requirements covering some of the types of data that were being stored in the analytics system.  These boiled down to ensuring that only authorised accounts could access the system and view information.  In my opinion the authentication/authorisation approach we've taken should be considered for any xDB installation as a good practice, however the explicit encryption requirements that we had to meet are probably a step further than a lot of organisations will want to go. ...

Enterprise Sitecore xDB High Availability with MongoDB

Image
As you may already know, Sitecore v7.5 and above has replaced the SQL Server based DMS technology that it has been using for analytics and replaced it with a new approach that uses the No-SQL technology MongoDB for capturing analytics data. Sitecore has a cloud xDB offering available in some geographies (alas it hasn't come to Australia yet!) but we recently delivered an xDB implementation for a client who needed to house their analytics databases on their local hosting infrastructure. This meant that we had to consider how to meet some of the enterprise requirements with Mongo that we had been pretty comfortable dealing with in DMS with SQL Server.   In particularly our high availability and security requirements had to be addressed slightly differently. This will form the first part in a two-post set outlining some of what we learnt along the way.  The second post deals with configuring Sitecore and MongoDB for enterprise security requirements . High Availability...

Customising the experience for Sitecore AD users

Image
In the overwhelming majority of Sitecore installations that we deliver for clients, content authors want to use the Active Directory integration module to login to Sitecore -- understandable, who wants to have another login!  As outlined in my previous post about recursive AD synchronisation , it is actually quite simple to set up the Sitecore AD module to use your AD roles and user accounts to enable Sitecore login. One of Sitecore's little idiosyncrasies is that by default it will log you in to the content editor application, which I find is the least useful thing for most content authors.  Generally we want to log content authors into the Sitecore Desktop.  This is not a setting that you can set on a role, instead it is a setting of the user's profile. You can definitely go an individually update each of the users that have been created by the  AD module to by default log the user into the desktop, but we don't want to have to do that every time we create a...