No topic on ASP.NET CMS platforms would be complete without talking about the database. In an agile decoupled content management and deployment model, a relational database presents challenges. Content needs to be managed in a more structured (or intelligent) manner than a Blob provides. What's required is a flexible content or data model, offering a richer content structure, and that's where NoSQL can help.
In the third installment of our series on ASP.NET Web CMS we talk content: Structured vs blob. In a multi-channel, multi-device world, the ability to reuse content is absolutely critical. Content reuse takes a variety of forms. It could be the updating of content on multiple websites or mobile devices, supporting multilingual requirements, or it could involve content for both digital and print. The idea of creating and managing separate versions of content for each channel/device screams of wasted time and effort. No one is crazy enough to do it this way (we hope!).
In this piece of our series on ASP.NET Web CMS we dive into development models. ASP.NET Web Forms is the traditional development model for ASP.NET. The problem with Web Forms is that it supports a tightly coupled architecture, one where the interface is integrated with the application functionality (code behind). MVC (model view controller) provides a different architectural pattern for development. MVC is the more modern approach to ASP.NET development, and is the future of ASP.NET with full support from Microsoft.
As you evaluate ASP.NET CMS solutions for your company, it's important to understand four key differences and how they impact your online capabilities and web experience road map. In this blog series we'll examine these four differences, explaining why they are important to understand and what each means for your decision process. Let's kick things off with the ASP.NET Web CMS architecture model.