For example, Next.js for Drupal allows components to build Drupal out of the box. Interesting contributions are happening to provide more JavaScript out of the box. For example, connecting layout-builder with front-ends out of the box. Where can Drupal improve? By connecting its powerful site-building system with JavaScript front-ends out of the box. Whether you need to consume or interact with an outside service or make use of data inside our digital experience platform, a powerful Hybrid Decoupled model ensures there are no limits to what you can achieve. With over 45,000 Drupal modules, you can integrate with all the back-end systems you need to keep your business moving forward. It can serve your needs when it comes to connectivity and a flexible delivery model. With JSONAPI, GraphQL, and native support for custom REST endpoints, Drupal delivers the Hybrid Headless model. Being able to deliver content multi-channel to improve customer experience across channels is creating a more interactive experience for wizards and search for example. Is headless in itself a selling point? No. It's how you balance and create value with it, that's the question. Being microservice or not is not the question. Core brings value in the sense that a lot of choices have been made through 20 years of evolution. I believe Drupal is striking a great balance between microservice and monolith. On the other hand, this is needed to build ambitious digital experiences and give all that no-code/low-code power to the site builder while maintaining developer freedom.įinally Drupal is based on Symfony which gives you the possibility to develop custom parts in the application by overriding existing code. Yes, there is a certain maintenance cost to Drupal and there is a level of complexity and dependency present. Maintaining Drupal has never been easier either. It's also the foundation of industrialisation in an agency, being able to implement all projects the same way allows for maximum maintainability.ĭrupal moving to automatic updates is a good thing. This re-usability is the foundation of contribution. For developers, knowing there are standards the framework brings, allows them to easily take over projects, so less need for heroes saving the day. As a customer, having the possibility to move your project to another integrator gives you lots of freedom too. So a bit of packaging and creating valuable dependencies out of the box has a lot of value. Having a standard in Drupal on how modules interact with core creates stability and allows the 1M strong Drupal community to maintain the 45k module ecosystem of functionality. Monoliths are often called a big ball of mud, microservice can easily become a big distributed ball of mud. That's not acceptable for every organization. On the other hand, there are enough examples of DIY microservice hell, where customers need to hire people to maintain all these microservices, do release management, DevOps, and maintain knowledge of all the separate services. A lot of risks are introduced for the sake of speed. with multiple integrations for multiple personas experiences. While core still does a lot, it is this interdependency of data, users, and content that allows building the more ambitious multi-languages, countries, markets, channels, roles, sites. In Drupal 11 this trend will even accelerate. However, Drupal's core is getting smaller and smaller, moving more and more core modules to contrib modules. If we take a step back and look at the modular architecture of Drupal we see that indeed yes Drupal core does a lot of things and could be deemed monolithic.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |