The Lucid Architecture for Building Scalable Applications - Given at LaraconEU 2016 by Abed Halawi
Developing large-scale applications has always been easy to think about but when it comes to implementation, complexities start laying themselves on the table especially when working in a collaborative team where decisions are peer-discussed and made over coffee or beer on a napkin. Moreover, with the rise of the microservice architecture trend, where dissecting the monolith you’ve always been working on becomes the next big thing in the project, the need for guidelines and standards becomes crucial for the task to reach success. In this opinionated architecture, you’ll learn about patterns that, when followed, will serve answering questions like "Where should this good piece of art code reside (folder, file, class, etc.)?”, "What design patterns should we apply to implement this feature?”, “What features are implemented in this project?”, “What are the different steps to accomplish a specific feature?”, and most importantly will make your monolith-to-service transition easier.
Recommandé
Recommandé
Contenu connexe
Dernier
Dernier (20)
En vedette
En vedette (20)
The Lucid Architecture for Building Scalable Applications - Given at LaraconEU 2016 by Abed Halawi
- 1. The Lucid Architecture Building Scalable Applications Abed Halawi - Tech Lead at Vinelab @mulkave
- 2. What is an Architecture?
- 3. What is an Architecture? Pattern of connected Structures
- 6. Structure
- 7. Architecture
- 8. An expression of a What is an architecture? viewpoint
- 9. Why Do We Have Them?
- 10. Why Do We Have Them? Communicate Structures Controller ✅ Model ✅ View ✅ Service ⁉ Domain ⁉
- 11. Why Do We Have Them? Eradecate Homelessness of Code 0 25 50 75 100 0 25 50 75 100 v1.0 v1.2 😈👺
- 12. Why Do We Have Them? Eradecate Homelessness of Code
- 13. Why Do We Have Them? Illustrate Structures Request Http Kernel Closure Controller Route Process & Respond DDD? Technical Debt 🤑 SOA?
- 14. Legacy Code
- 15. • No More Legacy Code • Defines Terminology • Comprehensive, No Limitations • Complements Laravel’s Design • Simple, Yet Sophisticated • Performs at Scale What? How? 🤔
- 16. Lucid
- 17. Lucid
- 19. Lucid • Feature • As described in business, as a class name • Runs Jobs - Steps in the process of accomplishment CreateArticleFeature LoginUserFeature Controller Process & Respond Feature serve
- 20. Lucid • Feature • Controllers serve Features
- 25. Lucid • Job A class that does one thing; responsible for the business logic • CreateArticleFeature • Validate Article Input • Generate Slug • Upload Files To Cdn • Save Article • Respond With Json
- 26. Lucid • Job A class that does one thing; responsible for the business logic • CreateArticleFeature • ValidateArticleInputJob • GenerateSlugJob • UploadFilesToCdnJob • SaveArticleJob • RespondWithJsonJob
- 27. Lucid • Job A class that does one thing; responsible for the business logic Controller Feature serve Validate Input Generate Slug Upload Files To CDN Save Article Respond With JSON ]Process & ] Respond
- 32. 1 3 2 1 2 3
- 33. Lucid • Service Implements Features and serves them through controllers Website Api Backend
- 34. Lucid • Service • Website • ListArticlesFeature • GetPublishedArticlesJob • RespondWithViewJob • Api • ListArticlesFeature • GetPublishedArticlesJob • RespondWithJsonJob • Backend • CreateArticleFeature • ValidateArticleInputJob • SaveArticleJob • RespondWithViewJob
- 35. Lucid • Service • Website • ListArticlesFeature • GetPublishedArticlesJob • RespondWithViewJob • Api • ListArticlesFeature • GetPublishedArticlesJob • RespondWithJsonJob • Backend • CreateArticleFeature • ValidateArticleInputJob • SaveArticleJob • RespondWithViewJob
- 36. Lucid • Service • Website • ListArticlesFeature • GetPublishedArticlesJob • RespondWithViewJob • Api • ListArticlesFeature • GetPublishedArticlesJob • RespondWithJsonJob • Backend • CreateArticleFeature • ValidateArticleInputJob • SaveArticleJob • RespondWithViewJob
- 37. Lucid • Service Http Kernel Which Service? Controller Feature Website Route Controller Feature Api Route Controller Feature Backend Route example.com api.example.com OR example.com/api admin…com OR example.com/api Domains
- 38. Lucid • Domains Responsible for the entities; exposing their functionalities through Jobs
- 39. Lucid • Domains • Article • GetPublishedArticlesJob • SaveArticleJob • ValidateArticleInputJob • Cdn • UploadFilesToCdnJob • Http • RespondWithJsonJob
- 40. Lucid • Layers Service Domain Data F A T U R E E J O B M D E L O
- 41. Lucid • Principles ✍ 1. Controllers serve Features 2. Avoid Cross-Domain Communication 3. Avoid Cross-Job Communication
- 42. Getting Started > composer create-project lucid-arch/laravel my-project 1. Init a project > lucid make:service Api 2. Scaffold a Service > lucid make:feature Api LoginUser 3. Generate a Feature > lucid make:job User CheckCredentials 4. Generate a Job
- 43. Lucid • Console