Weighing the Majestic Monolith vs the Separation of Concern in your Drupal Application
Drupal can be used to build a startup that scales, or as a critical foundation for an enterprise-grade public-facing web application.
Patterns that follow the "separation of concern" provided by microservices and decoupled Drupal become important when considering best practices for growing/maintaining applications at scale.
The "majestic monolith" architecture that Drupal fits provides much of the functionality that would take longer to build with only microservices and custom code, Drupal handles functionality such as logging, user management, and authentication all out-of-the-box in one centrally located codebase. However Drupal also offers the ability to migrate this functionality to microservices as you scale, for example porting users from Drupal to Amazon Cognito.
On the hosting and DevOps side, We will also consider SAAS/PAAS DevOps platforms and compare them against cloud services such as AWS, Azure and GCP. In what cases are these platforms the best choice for your bottom line and when is moving to a more complex DevOps pipeline based on the custom configuration of microservices reasonable?
We will also consider when it would be a good choice to forgo Drupal completely, using a decoupled frontend that relies completely on a microservices backend. We will cover the experiences we have encountered here on various projects and highlight the unexpected investment that orchestrating these various systems can incur.
Drupal - A better way to build Enterprise grade applications
As software developers building or maintaining software, we often find ourselves thinking "There must be a better way to do this”. The frustration stems from having to spend at least half of the development budget on doing the same thing over and over again. We seek out new languages and new tools, because we cant bear the thought of writing the same code for authentication, logging, caching, data access, db tables, themes, validation, deployment, testing etc etc etc. This session briefs out some of the challenges in developing an application from scratch and talks about "Drupal - The better way"
Cross platform apps and PWAs powered by Drupal for everyone
Every organization, every budget, and every timeline can be a perfect case for an app powered by Drupal. Published on the app store, stable, and often indistinguishable from a native app, PWAs can be a perfect solution to reach your goals on time and on budget.
Progressive web app technology coupled with cross-platform frameworks and native code can be used to optimize the development process and get your app delivered using web technologies familiar to a wider range of developers. The end result is a more stable and polished product.
This presentation will include my story of creating a successful business based on an app for both iOS and Android that uses PWA technologies and native code. All powered by Drupal.
We explore projects supported by Google for PWAs such as Bubblewrap and workarounds for iOS including PWA builder's recent adoption of WKWebview, as well as custom code solutions for WKWebview.
Benefits of PWAs include
-Efficient timelines and budgets.
-Utilizing existing veteran development resources and technologies for a stable reliable experience.
-Enhanced SEO when integrated into a website.
-Limited network usage and offline functionality which is beneficial for those living in developing nations.
DrupalCon Portland 2022 Sessionize Event
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top