{"id":2622,"date":"2021-06-02T11:05:03","date_gmt":"2021-06-02T10:05:03","guid":{"rendered":"https:\/\/www.cedar-bay.com\/?p=2622"},"modified":"2023-11-28T11:03:12","modified_gmt":"2023-11-28T11:03:12","slug":"why-you-need-an-integrated-stack","status":"publish","type":"post","link":"https:\/\/www.cedar-bay.com\/why-you-need-an-integrated-stack\/","title":{"rendered":"Why you need an Integrated Stack!"},"content":{"rendered":"
It\u2019s been said that the technology industry tends to go in circles. A more generous assessment might be that it iterates, with each cycle improving on the last.<\/p>\n
Twenty years ago, the strategy was to cobble together applications that provided the requisite depth of functionality to fulfil a particular business need: best-of-breed. The overall success of the approach was often determined by the ability of vendors and clients to integrate those applications into a cohesive solution.<\/p>\n
It resulted in future pain relating to the highly varied life cycles of the components involved in almost all cases. No sooner had you got your overall solution live than one or more vendors were announcing their sunsetting schedule, which meant revisiting the integration, and so on.<\/p>\n
The industry response to this was the \u201cSuite,\u201d the complete range of functionality you require from a single vendor. Many vendors pursued \u201cSuite\u201d status by acquiring point solutions and weaving them into their core offering. The result looked good on paper; the integration and product life cycle challenge had been transferred to the vendor.<\/p>\n
In reality, the \u201cSuite\u201d often diluted the depth of functionality available. Usability suffered as vendors struggled to apply a veneer of commonality across a product comprised of very different technologies. Although benefiting from a single roadmap, upgrades became hugely complex, with significant releases often leveraged by vendors to streamline the underlying technology.<\/p>\n