Monolithic installs VS single responsibilities networks
1 like354 views
The document discusses moving from monolithic Drupal installations to a microservices architecture. It notes that large Drupal sites can become unstable and difficult to update as they grow in size and complexity. The microservices approach breaks the site into independent, specialized services that communicate through APIs. This allows each service to focus on a single task and improves scalability, stability, and ability to update individual components. The talk provides an overview of how to plan and implement a microservices network for an existing Drupal site, including defining service roles, development tools like Docker and Ansible, and monitoring with Logstash and Kibana.
Monolithic installs VS single responsibilities networks
- 1. Monolithic installs VS single responsibilities networks Fedir RYKHTIK DrupalDeveloperDays 2015
- 2. About speaker Fedir RYKHTIK CTO @AgenceStratis (Toulon, France) Drupal developer since 2008 DrupalMeetup organizer White elephants handler @FedirFr
- 3. Talk summary
- 4. The problem
- 5. Sometimes drops begins to be too big
- 6. Big heavy sites ● Some times not stable ● Lots of hooks ● Lot’s of operations ● Lot’s of usage scenarios ● Difficult to update ● Difficult to migrate ● Difficult to scale
- 7. 99% of time You don’t need ALL modules / hooks at the same time
- 8. Drupal’s Site Usage Scenarios ● Content administration ○ Permissions ○ Workflow ■ Validation ■ Content programmation ● Content automatic importing ● Exporting content (REST/RSS) ● Showing the content
- 10. Microservice In computing, microservices is a software architecture style, in which complex applications are composed of small, independent processes communicating with each other using language-agnostic APIs. These services are small, highly decoupled and focus on doing a small task. http://en.wikipedia.org/wiki/Microservices
- 12. “There are certain things you need to get sorted out before you can put your first microservices system into production: monitoring, provisioning, and a devops culture.” Martin Fowler http://martinfowler.com/bliki/MicroservicePrerequisites.html
- 14. Provisioning
- 15. DevOps tools
- 16. System Architecture description ● Vagrant wrapper on local machines ● Docker + Ansible in production ● Ansible Tower for efficient control
- 17. Monitoring
- 18. Efficient logging for the best visibility & collision detection ● LogStash ● Kibana ● monolog ● Drupal’s “Log HTTP” project
- 19. HowTo
- 20. ● Content import ● Content administration ● Content rendering ● Front end caching ● User management Define service roles
- 21. Transformation of an existing site into microservice network ● Find a white elephant ● Detect the services in use ● Describe flows of connection ● Create the network via DevOps tools ● Create & test standalone services ● Connect flows ● Pack it up ● Deploy
- 22. Books to read
- 23. Links ● http://en.wikipedia.org/wiki/Microservices ● http://en.m.wikipedia.org/wiki/Service-oriented_architecture ● http://fr.slideshare.net/TylerTreat/from-mainframe-to-microservice-an-introduction-to- distributed-systems-41004778 ● http://martinfowler.com/articles/microservice-testing/ ● http://martinfowler.com/bliki/MicroservicePrerequisites.html ● http://martinfowler.com/articles/microservices.html ● https://www.loggly.com/blog/logs-for-drupal-why-you-need-them-and-how-to-do-it/ ● http://www.slideshare.net/slideshow/embed_code/key/464TyWARPmjno8 ● https://wooster.checkmy.ws/2014/04/elk-elasticsearch-logstash-kibana/ ● http://odolbeau.fr/blog/when-monolog-meet-elk.html ● http://fr.slideshare.net/jamtur01/yes-logging-can-be-awesome ● https://github.com/victorlin/ansible-docker-demo
- 24. Q&A Any questions ? Let’s talk ! :)
- 25. Thank You