The whys and the why nots of custom code, frameworks, accelerators, and products

There is no one fits all when it comes to IT architecture. There are so many different needs and objectives to be met – and so many concepts to get you there. 

But what are actually the advantages, disadvantages, and differences between those concepts?

It's typically after implementing an IT architecture – once they start grappling with high maintenance expenses, inflexibility, and strained customer/supplier relationships – that clients realise any downside to the conceptual choice they made.  

When our friends in Alokai asked our CEO Toke Lund to guest write for their blog, he jumped into custom code, frameworks, accelerators, and products.

The blogpost is his attempt to help decision-makers make their tech choices with open eyes.

👉 If you want to read his blogpost, and you should, just jump to Alokai and give it a whirl. 🤓