3 ms·
Drupal is going after the enterprise content management market, and offers 3 benefits. 1) You can buy enterprise software support from Acquia. 2) It's relativ
by snowwrestler 11y ago
Drupal is going after the enterprise content management market, and offers 3 benefits.
1) You can buy enterprise software support from Acquia.
2) It's relatively easy to find Drupal coding talent.
3) The community cares a lot about security.
Talented developers will find custom solutions more enjoyable and efficient to create and operate. But a custom content application loses to Drupal on all 3 of the above points.
- lkrubner 11y agoWhat do you mean when you write "a custom content application loses to Drupal on all 3 of the above points"? Consider this: http://www.indeed.com/jobtrends?q=drupal%2C+node%2C+rails&l= http://www.indeed.com/jobtrends?q=drupal%2C+node%2C+rails&l= There is a lot of custom work in the Enterprise. It dwarfs any one CMS. Also, about #2 in particular, do you think it is hard to find Node talent or Rails talent? They both seem fairly abundant to me. Regarding #1, I'm sure you can recognize this as a double-edged sword: "You can buy enterprise software support from Acquia." That is the problem, the Enterprise support is associated with a single company. Unlike, say, Rails development, or especially Java development, where there are a zillion companies selling to the Enterprise. The problem for Drupal is in trying to find that space between "too big for off-the-shelf" and "too small for customized solution". It's a very narrow space.
- snowwrestler 11y agoWhat I should have said above is that Drupal is a more narrowly defined product than Rails or Node or other frameworks. Drupal 8 is moving toward a "framework" approach, but it's still just a "web content management framework." So for the people who just need to manage web content, Drupal will have the advantages I list above. It's more a matter of being better fit for a particular purpose, than some inherent superiority of technology. For building software products in general, including in-house enterprise products, Node, Rails, and others will still be winners. But for managing web content, Drupal comes with enough functionality, security, and developer support out of the box that it will beat custom solutions a lot of the time.
- hunvreus 11y agoEnterprise moves slower, but I doubt that after another Drupal development cycle (5+ years) the momentum will still be there. Sure, there will be plenty of legacy Drupal sites to maintain, but I have a hard time imagining developers even in very corporate context using it when they can address these points with more modern approaches. For example using a content API like Contentful or equivalent and building simple front-ends that scale and are secure: no need for 4 layers of caching when you're basically serving static assets. As long as your API is secure, you're good to go. And finding folks who can write JS, HTML and CSS is a lot easier than finding Drupal "experts".
- snowwrestler 11y agoDrupal is evolving toward what Contentful does, and Drupal brings a huge international community and customer base with it. Companies are already building sites this way with Drupal--the Tonight Show with Jimmy Fallon is a pretty high-profile example. You would have no idea from the front-end code that Drupal is managing the content on that server, but it is.
- hunvreus 11y agoI believe one of the main reasons Drupal got popular was the module ecosystem. A move towards what you describe would likely erode this aspect, with many more user friendly and maintainable alternatives.