In this article we will try to explain the buzz, what Headless actually is and how, when and for whom Headless is the right way to go and when not.
In its simplest form headless can be explained as the front-end being separated from the back-end with an API, relieving the front-end from any constraints of the back-end.
Most companies experience a strong drive for adding new digital channels, to improve their digital customer experience and to increase speed and agility in development to keep up with or beat competition. That is part of the context that influences and feeds the headless frenzy. But there are more reasons why headless provides a compelling set up for your digital architecture.
Headless is not a silver bullet or a strategy that all can benefit from. Generally you can say that it is a more demanding set up and requires a certain level of maturity both when it comes to digital thinking in general but also in technical know-how.
If you do not plan to employ a standing development team inhouse or external that constantly run sprints to evolve your digital channels - headless is not for you.
If you do not plan to launch multiple front-end applications or make use of a separate CMS - headless is not for you.
Headless scenarios
There are multiple scenarios that can be defined as headless with specific setups that support different strategies. In this section we bring up a few examples to describe potential scenarios.
A. Separate front-end from back-end. |
In its purest form separating the front-end from the back-end by consuming the back-end logic through an API. Scenario A could be seen as a starting point developing into any of the following. |
B. Multiple front-ends to one back-end |
Powering several touchpoints with the same back-end. For example one of more websites and native Android/iOS apps. One source of truth and one single platform is beneficial both for users/customers of the frontend and also for editors/administrators. This approach also enables the switch between touchpoints to be more seamless for the user. |
C. Multiple back-ends to one or many front-ends |
To really support a best of breed strategy you can connect several back-ends to your front-end(s). A CMS, ECOM, PIM, DAM, CRM, OMS or whatever acronym you believe will benefit your set up. One step closer to the headless nirvana you might be looking for. ;-) |
D. Multiple back-ends with orchestrator to front-end(s) |
Decoupling the components of your solution will require some orchestrating logic. It has to be put somewhere, either as part of the front-end, as an api layer between the back-end(s) and the front-end(s). This is often referred to as a BFF - back-end for front-end. This will add some complexity but it also provides clean cuts and will make the components more interchangeable. |
Litium is a complete suite that includes CMS, PIM and Ecommerce, ready for Headless using our API or for swift go-to-market using the best-practise Ecommerce Accelerator front-end available.
Scenario A + B, use all the built in functionality in Litium to handle everything from content to orders and connect any front-end using our Headless API.
Scenario C, if you have a favourite CMS you can use it side-by-side with Litium adding extensive PIM and e-commerce functionality.
Scenario D, the back-end for front-end is supposed to handle the orchestration and business logic to produce a coherent user experience making best use of different special purpose back-end platforms. Developing this BFF API could almost become a platform of its own so instead you can use Litium as the orchestrator bringing in content from your CMS, PIM, CRM, DAM etc. making the content come alive with the right business logic.
Hybrid scenario, perhaps you want to direct your effort to customer facing touch points but still are in need of internal portals etc. With Litium you can apply a hybrid strategy combining headless for some front-ends and the Litium best-practices Ecommerce Accelerator for front-ends where you do not benefit from custom developed experiences.
Want to know more about Litium? Read more about Litium and headless here or contact us at curious@litium.com.