One of the great challenges facing traditional ERP vendors is getting
customers to keep up with the latest version. Cloud ERP systems are
supposed to solve this problem, by making the vendor responsible for
upgrades and keeping all customers on a single version.
However,
sometimes, even SaaS providers need to make changes that are so
significant and potentially disruptive that customers resist the change.
Read the rest of this post on the Strativa blog:
Getting ERP Users to Upgrade—Cloud vs. Traditional Systems
2 comments:
Hi Frank,
Interesting...
Having two systems is still better than the dozens of different production versions of on premises ERP.
An incidental benefit of this sort of “dual system” approach is that it reduces risk when deploying new code and technology, particularly when the newer part is in its infancy.
Also, newer architectures (as you mention) enforce a clear demarcation between standard and custom functionality - thereby avoiding code contamination. Such architecture should prevent entanglement with "customer funded development" from occurring.
Regarding microservices architecture, this is significant because it permits a gradual progression from old to new. Components can be progressively swapped out one-by-one, without the big risks associated with changing a monolithic system. Microservices architecture also allows the mixing and matching of different development technologies and components rather than coding everything in one, thereby establishing an enterprise ecosystem that lends itself to survival of the fittest.
Cloud ERP (NetSuite)is faster and easier to deploy than on-premises ERP systems (SAP Business One).
Post a Comment