3 ms·
Very curious what they will do with this. Demandware is horrible to develop for.
by JoshGlazebrook 10y ago
Very curious what they will do with this. Demandware is horrible to develop for.
- stanmancan 10y agoIt can't possibly be any worse than developing for Salesforce.
- JoshGlazebrook 10y agoI've not personally touched Salesforce, but demandware centers around "pipelines" which essentially I would equate them to a visual route handler/middleware combination. Which works in combination with their propriety scripting language (javascript based), templating system, etc. pipelines: http://blog.baha.dk/content/images/2015/12/dwpipeline-1.png http://blog.baha.dk/content/images/2015/12/dwpipeline-1.png general overview: http://blog.baha.dk/2015/12/19/part-2-developing-demandware/ http://blog.baha.dk/2015/12/19/part-2-developing-demandware/
- stanmancan 10y agoSalesforce has its "server" side language APEX which is sort of kinda based on Java, then they have SOQL which is their own, limited and akward version of SQL, and Visualforce which is their front end. So many limitations that make no sense. Documentation rarely tells you the whole picture. The whole thing is full of gotchas that you only learn through experience. Ugh.
- microcolonel 10y agoFor what it's worth, in production Demandware is much better than Websphere Commerce Server. WCS could very well be cleaner in some universe, but the heavily-customized (thanks IBM) versions that run in actual enterprise retailers are hellish. I worked with a team which put together a complete ecommerce site using mostly their standard http APIs in a couple of months, and unlike the WCS deployment I dealt with, Demandware was usually working. We did run into plenty of bugs, but the account manager got them resolved in short order. I would agree that, assuming no other context, Demandware is awful. In the context of its competitors, it feels like a breath of fresh air.
- zippergz 10y agoAmazingly, it is. A match made in heaven.