DDAY2014 - Drupal 8 e il mercato Enterprise: questo matrimonio s'ha da fare?
•Télécharger en tant que PPT, PDF•
0 j'aime•842 vues
Speaker: Daniele Piaggesi Area: Business, PA La release 8 di Drupal sarà quella che lo consacrerà come strumento veramente spendibile anche nel mercato enterprise. Ma cosa dovrebbe convincere i "decision maker" di Telco, multinazionali, pubblica amministrazione a scegliere il CMS dalla goccia blu?
Recommandé
Contenu connexe
Similaire à DDAY2014 - Drupal 8 e il mercato Enterprise: questo matrimonio s'ha da fare?
Similaire à DDAY2014 - Drupal 8 e il mercato Enterprise: questo matrimonio s'ha da fare? (20)
Plus de DrupalDay
Plus de DrupalDay (20)
Dernier
Dernier (20)
DDAY2014 - Drupal 8 e il mercato Enterprise: questo matrimonio s'ha da fare?
- 2. Who am I? • System Architect • PHP Programmer • Opensource Expert • Drupal Evangelist (and developer) • bmeme (http://bmeme.com) founder daniele.piaggesi@bmeme.com @g0blin79
- 3. What is bmeme? WE BUILD WE SUPPORT WE TEACH
- 4. Agenda • A brief disclaimer… • What do we usually mean for “Enterprise market”? • Drupal in the Enterprise Market • How Drupal 8 can meet Enterprise needs? • A true story… • …and if this story had taken place in an year...
- 5. First of all a Disclaimer… this talk is not for NERDS NERDS NERDS NERDS
- 6. Now we can go on…
- 7. What we usually think of when we talk about “ENTERPRISE MARKET”? “ENTERPRISE MARKET”?
- 9. Characteristics • Complex environments and architectures • Complex (and sometimes old) processes and tools • “Paranoid way of life” • High level of bureaucracy • Poor attitude to changes
- 10. Keywords • High availability / Fault tolerance • Reliability • Scalability • Safety and Security • Interactions • Continous Integration • …Patience…
- 11. Drupal in the Enterprise Market Enterprise Market
- 12. Drupal enterprise experiences Drupal is not new in Enterprise Market. Enterprise projects in which bmeme is/was involved in these last years: •European Community •TelecomItalia •United Nations - World Food Programme
- 13. What about Drupal 7? Drupal 7?
- 14. #mmmhhh
- 15. Limits of Drupal 7 • Incomplete Entity API • A lack of separation between content and configuration • A lack of separation between logic and presentation in the theme layer • “Drupal-specific” language (that creates a non-standard) • Procedural programming • Deployment http://buytaert.net/why-the-big-architectural-changes-in-drupal-8
- 16. The first step over Symfony http://buytaert.net/why-the-big-architectural-changes-in-drupal-8
- 17. But what Symfony means? means?
- 18. Symfony means… • Object Oriented Programming instead of procedural programming • Coding standard instead of “Drupal-specific” language • Configuration Management instead of Features • Twig instead of phptemplate
- 19. …and also… • Test-drive development • Continuous integration • Support of libraries, standards, security parameters, RFC • Integration by-design with third-party services http://buytaert.net/why-the-big-architectural-changes-in-drupal-8
- 20. …and finally. • More programmers, themers, site builders that can be called Drupal developers. • The power of two frameworks in one product • The possibility to integrate in D8 Symfony libraries and bundle not event covered that can add new functionalities
- 21. on the other hand everything was changed! everything was changed!
- 22. #whatthefuck
- 23. Some interesting D8 news D8 news
- 24. What’s behind… • Mobile First • Multilingual Capabilities • Configuration Management Initiative • Data Migration API • Cache API • Web Services API • Less modules for faster page loads and reduced server load. • some other more :)
- 25. Q&A ?