Category
14 articles in Architecture
'Go headless, and the hard part is solved.' A claim I have heard many times in recent years. The freedom to pick isolated systems that fit your specific needs, that can be swapped out, that can scale, where you pay only for what you use. It sounds like a dream. But if it really is that simple, why is not everyone doing it?
As the various systems used in digital commerce become more capable, the complexity of deciding where information and logic should sit only increases. The most common systems in use today for retail and e-commerce were built at a time when things were more isolated. So how should you think about it today?
Keeping accurate stock levels for your items across all systems is a harder problem than it might first appear. How much revenue are you losing because you do not dare trust your own stock levels and always keep a buffer to be on the safe side?
Choosing an e-commerce system is something you end up doing surprisingly often as a successful e-commerce operator. You start with a simple system that you outgrow. You switch, some things get better, some get worse. A few years later it is time again. But how do you choose the right one? How do you avoid buying a pig in a poke?
React is without a doubt the most popular choice among frontend frameworks. But does that mean it is the right choice for you? How much does the choice of framework really matter? What are the pros and cons? What are the alternatives?
