Spryker OS--Enterprise solution for large, ambitious products

In this case I am giving my opinion on support for Spryker Cloud Commerce OS from a developer's perspective on their support for modules, feature sets, and security updates. Most of the time it is easy to update Spryker modules; however, there might be a lot more problems when handling major version updates that might require lots of time to adjust to. And sometimes even smaller updates that should be compatible might break the system (especially having in mind how the early version of it differs from the current one). However, they are transparent about it and do not recommend updating modules without an explicit need for it. It might be tough if what breaks is security related and cannot be avoided.

The Spryker team themselves are effective with resolution of given questions--they respond fast and can provide consultation if need be. I haven't had the need for a lot of direct support, but with the little experience I had, I am satisfied with their technical support.

Extendable, maintainable, changeable--all the best practices are there to use and adjust. It is difficult to exploit all that Spryker Cloud Commerce OS has to offer from the get go as it is complex and can be a bit overwhelming at the start.

For long-term large e-commerce (or feature-heavy) projects Spryker Cloud Commerce OS is a great choice, as its architectural decisions help to keep up development pace in late phases of the project. It has one of the cleanest code bases acting as a reference as well as documentation for developers. If multiple projects are developed with Spryker Cloud Commerce OS, the team can be interchangeable, as the architecture ensures unified project layout. However, Spryker Cloud Commerce OS has its use cases--I wouldn't recommend it for small projects or without having experienced developers to work on it.