*Note – this post assumes that a platform like WordPress isn’t sufficient for your requirements

Where to start?

If you look at https://en.wikipedia.org/wiki/List_of_content_management_systems, it certainly won’t clear things up. There are a LOT of options! So, what sort of information should you use to feed into your decision process?

A few core CMS concepts

Before we go further, let’s define a few key concepts:

• Headless Content Management System (CMS) – “A headless CMS is a content management system that provides a way to author content, but instead of having your content coupled to a particular output (like web page rendering), it provides your content as data over an API.” https://www.sanity.io/blog/headless-cms-explained
• Digital Experience Platform (DXP) – “Gartner defines a digital experience platform (DXP) as an integrated set of technologies, based on a common platform, that provides a broad range of audiences with consistent, secure and personalized access to information and applications across many digital touchpoints.” https://www.gartner.com/reviews/market/digital-experience-platforms

It’s worth noting that certain vendors aim to fulfil both entries above, whereas others operate purely as headless, cloud native SAAS providers.

How to help you make a decision?

Ah, but what if the decision has already been made?

Within your team(s) or business(es), do you have an existing CMS? If so, can it be scaled or modified to serve your new needs. It’s worth considering that ‘scaled’ here covers many things – licensing, usability, modifiability, supportability, physical capacity and a raft more. This discussion often leads to some interesting outcomes and can easily expose issues, or the opposite, a positive view of existing tooling.

Ok, so we already successfully use CMS X

We’re getting warmer, but I’d suggest you still need to answer a few more questions:

• Is it fit for purpose?
• Do it’s content delivery approaches fit the needs of your new requirements?
• Will the team that use the system be the same as the existing editors?

How to select a new CMS?

I’d recommend you build up your own criteria for assessing different tools, here are a few thought starters:

• Cost
  • What are the license fees, and how do they scale?
    • Is it a consistent cost year by year?
    • What if you need more editors?
    • What if you need more content items, or media items?
    • What if you need to serve more traffic?
    • How much would a new environment cost?
  • How much does it cost to run and maintain the system?
    • What hosting costs will you incur?
    • How much does a release cost?
    • What cost lies with your different DR options?
    • How will the infra receive security patches and software upgrades?
    • What does an upgrade of the tool look like? Is it handled for you, or do you need to own an upgrade?
      • Note. This has stung us hard in the past with certain vendors!
  • How much effort/cost is required to set it up before you can focus on delivery of features to the customer?
• Features
  • Does the tool support the features you require?
  • Or, does the tool come with features you don’t require?
    • This is an interesting point – are you buying a Ferrari when all you need is a Ford?
  • Are your competitors using the same tool?
    • Does it suit your business model?
  • What multi-lingual requirements do you have?
    • And how does that map to content and presentation?
• Technology constraints
  • Are there any technology restrictions imposed by the tools
    • E.g. hosting options, language choices, CI/CD patterns, tooling constraints
    • Who owns the hosted platform, and how do backups work?
    • Does the location of data matter for your business?
• Platform vs a tool
  • This ties into the concepts above, do you want a DXP or a headless CMS
  • Is a composable architecture desirable for your team(s)?
• Out the box vs bespoke
  • What comes ‘for free’? And, do you even want the ‘free’ features?
    • If we think of enterprise platforms such as Sitecore, you get a lot OTB for free. E.g. the concept of sites, pipelines, commands and many more.
    • If you go down the headless route this lies in your dev teams hands.
• Building a team
  • Can you even build a team around tool X?
  • Do you have in-house experience in the tool or associated tools?
• Support
  • What if something goes wrong, what support can you get?
    • Note, I’d see support running from before you sign the contracts all the way through to post live ongoing support
• Scalability, performance and common NFR’s
  • Will the tool scale and perform to your requirements?

It’s worth noting, this is not meant to be an exhaustive list – every project will have different requirements and metrics that get prioritized. The goal is to provide some thought starters in areas we’ve found useful in the past.

Finally, the fun part – rolling it out

Well, almost. Now the fun / hard part (omit for your preference :)).

You have your new tool, but how does it map to the business? How will the editors get on with it? What does multi-lingual design look like? What technology do you use to build the front ends? Where to start? What is the meaning of life?

Maybe that’s content for another blog post…

Happy editing!

The post Why is choosing a CMS so damn hard? appeared first on blog.boro2g .co.uk.

* Arguably the term you use here depends on how you choose to cut your system and services

What to expect

Well, maybe lets start with the opposite – what not to expect?

• This isn’t aimed to be a starter kit, it’s goal is to provide examples
• How you choose to cut up your apis, well that’s one for you too – sorry
• And finally, how you choose to name things (models vs data, services vs domain, core vs base, shared vs common) – yep, that’s also up to you

Now the good bits, what to expect?

The goal of the example project (https://github.com/boro2g/MonolithToMicroserviceApi) is to show working examples of the following scenarios:

• Each WebApi project can run in isolation, without knowledge of others
  • The same mindset applies to deployments – each WebApi can be deployed in isolation
• All the WebApi’s can be run and deployed as a single application

Why add this extra complexity?

Good question. The key thing for me is flexibility. If it’s done right you give yourself options – you want to deploy as a monolith, no problem. You want to deploy each bit in isolation, well that’s fine too.

How does it look?

Some key highlights of the image above:

1. MonolithToMicroserviceApi.WebApi
   1. This is the shared singular WebApi project that brings everything together
   2. You can run this via IISExpress, or IIS etc and all the Api’s from the other projects will work within it
2. MonolithToMicroserviceApi.Search.WebApi
   1. This is the search micro(macro) service
   2. You can run this in isolation, much like you can the common one
3. MonolithToMicroserviceApi.Weather.WebApi
   1. The same concept as Search, but with other example controllers and code
4. MonolithToMicroserviceApi.Shared.*
   1. These libraries contain common functionality that’s shared between each WebApi

Adding a new WebApi

The search project has a good example of this. If you look in MonolithToMicroserviceApi.Search.WebApi.Startup

You need to add the ApiConfiguration class itself (see the project for examples), the ApiConfigurations code above and then register them all.

Similarly in the common project startup (MonolithToMicroserviceApi.WebApi.Startup). Simply add each ApiConfiguration and register them.

The Api glue

So how does it all glue together? The key underlying code that allows you to pool controllers from one project into another is:

What issues you might run into?

• Routing
  • There is a commented out example of this – in the core project and weather project we have a ‘WeatherForecastController’ – if both of these have the same [Route] attribute you will get an exception.
  • A simple fix is to ensure each controller has isolated routes. I’m sure a more clever approach could be used if you have LOTS of WebApi projects, but I’ll leave that for you to work out

• Dependency bleeding
  • I don’t feel like this approach introduces any more risk of either cyclic dependencies or ‘balls of mud‘ – IMO that comes down the discipline of the team building your solutions.

Summary

What I like about this approach is flexibility. On day 1 you can deploy your common project to a single box and all your api’s are working in one place. Over time, as complexity grows, or your dev teams evolve, different parts can be cut apart but without any fundamental changes needed.

You need to scale your search api, well no problem – deploy it as a single api and scale as you need.

You need to push the weather api to multiple data centres for geo reasons, cut it out and deploy as you want.

Another team needs to own search, again thats fine – you could even pull out to another solution, remove the ApiConfiguration and everyone is happy!?

I hope it provides some good inspiration. It really doesn’t take much code, or configuration to build what I’d consider to be a very flexible approach to structuring your dotnetcore WebApi projects.

The post Monolith, microservice or something in-between appeared first on blog.boro2g .co.uk.