Comparing SDL Tridion

Tried comparing SDL Tridion with few other lead CMS system viz: Sharepoint, Sitecore and Kentico – not much from a very technical perspective but from a Business lead perspective; and below is the result:


Director at Content Bloom India having 15+ years of experience in Software Development Life Cycle using AGILE, Iterative and RUP approaches. Experience in following: - CMS packages: SDL Tridion, Adobe Experience Manager (AEM), Sitecore, Umbraco, Kentico, and Alfresco - Search Engines: SOLR, AWS Cloud Search, Elastic Search - .NET Technologies: .NET & .NET CE Framework, ASP.NET, ASP.NET MVC, WCF, WinForms - Mobile Development: Android Native App, Windows Mobile App - Database: MS-SQL Server, MySQL - Program Management: JIRA, MS-Project, Trello - Design Tools: MS-Visio, StarUML - Infrastructure: Linux, Windows Server, AWS Have decent knowledge about Core Java, Spring MVC Instrumental in Application Architecture, Designing (HLD & LLD), Coding and deployment .NET applications (Web, Desktop, Mobile). Experience in following domain: - Digital Media & eCommerce - Travel & Hospitality - Aviation Industry - Education - Insurance - Automation - Automobile - Railways Education: Bachelor Degree in Computer Engineering and Post Graduate Diploma in Business Administration with specialization in Marketing

Posted in SDL Tridion
5 comments on “Comparing SDL Tridion
  1. It is always interesting to see comparisons between CMS systems, so this is great.

    You may want to consider adding a note to the OS needed for Tridion, as the CM side has to run on Windows.

    You may also want to consider the use of the word ‘supported’, as this can imply that is it supported by the vendor (e.g. Tridion Support).
    For example, connecting to the Tridion OData webservice can be done from languages other than Java and .Net. however, it ‘support’ is probably ‘limited’ (e.g. only the OData call itself).

    Keep up the good work!

    • Pankaj Gaur says:

      Thanks John for the valuable suggestion.

      I will do the suggested changes and re-publish this article.
      However, the OS supported means is for the End-User Website and not the CMS system in itself – meaning SDL Tridion can support CMS capabilities for ASP.NET based website, Java based website and virtually any type of the website, whereas CMS systems like Sharepoint and Sitecore can provide support only for ASP.NET based website only

      • devender singh says:

        Can have your Cell no sir…. i have to take some guidance with respect to sdl tridion or solr search from your side… i will be very fortunate if you give some guidance in it.

  2. Doug Kulak says:

    In my opinion, this is entirely misleading. Separation of Content and Presentation, for example. Sitecore does this, and it does it extremely well, and across multiple devices… where are you getting this information from? Same goes with Scalable publishing architecture and API support. I know you said this wasn’t technical, but this isn’t even accurate.

    • Pankaj Gaur says:

      Thanks for your input – Not sure if recently there are any addition in Sitecore.

      Till the time I have worked upon on it and whatever little knowledge I have Sitecore, does not provide a separation between content and presentation (although it does but not 100%) – Imagine a scenario where I have to create a page (presentation) with different content for different languages or devices in “multiple” website (say with different DNS) – Would you create a single page (presentation) or multiple – If your answer is one – I would agree with your thoughts and if it is multiple – then it is clear Sitecore is not separating the content with presentation.

      On the API, yes Sitecore provide decent APIs to extend, but I am comparing where you have the APIs to directly interact with key processes – For Example: Publishing – This can be override in Tridion – I am not talking about an Event-Listener mechanism to catch event and inject the custom code but actual Override of Publishing process – Per my knowledge in Sitecore, the default publishing process can be modified by injecting code through Event-Listener mechanism

      On the Scalable Publishing process – For an example: Consider a batch publishing of 10000 items. Now consider two major component of the Publishing Process – Rendering and Deployment – Does Sitecore allows me to scale out the Publishing process without any impact on the Sitecore CMS infrastructure change? Per my knowledge, to resolve this in Sitecore, we need to put multiple server for the entire Sitecore CM in load balancing.

      Let me know your thoughts and if I am missing something existing/updated/recently added feature and I will be happy to update the blog šŸ™‚

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: