Determine Headless Commerce Platform Without Code Analyzing: Step #1
Below are some techniques for someone with business background to define a platform architecture: headless or monolithic. Why is this needed? For example, you research a list of available headless platforms to submit to the board of directors.
Of course, the easiest way that comes to mind is to ask each vendor if their platform is headless. There is one problem here. The vendor's response could be multi-word marketing text without directly answering your question about the platform architecture.
Therefore, here and below, we will consider several steps how you yourself can determine whether the platform is headless.
First, ask the vendor if you, as a customer, can remove or add certain features from / to the platform. Definitely, you shouldn't pay for unused features, which contradicts your rules to run your business economically. Moreover, redundant features mean extra code on the system that requires additional CPU power and server memory in the cloud or on-premises, which you also have to pay for, otherwise the system will be too slow.
If you get a response like “Well, you can't delete anything, just use the functions you want”, this most likely means that the platform is based on a monolithic architecture. By the way, when adding features is concerned, this is often possible as add-ons even in monoliths, albeit from a limited list of additional applications.
In a headless architecture, adding or removing functionality is possible by choosing any best-in-breed application available on the market without restrictions. But mind such applications from the market must have an external API for integration purposes.