Apps versus websites, Drupal’s place in a microservice architecture
Microservices are hot, and for a lot of developers that means Drupal 's not, but does it have to be like this?
I want to have an in depth talk about the place of Drupal in a decentralised, decoupled microservice architecture:
- Should Drupal be the trustworthy flexible content store, that feeds a plethora of apps that use Drupal's API with a series of microservices to build our webpages?
- How can we combine Drupal with lightweight applications written in Go or other languages that developers prefer over PHP?
- How do you split business logic between sites in a loosely coupled Drupal architecture?
- What is the right balance between centralisation and decentralisation?
This is a continuation of a discussion that was sparked by one of Dries' recent blogposts