Developing clean services using laravel
Download as PPTX, PDF0 likes282 views
The document provides an in-depth discussion of Laravel, a PHP web framework, focusing on its application lifecycle, class communication, and the implementation of an API. It addresses key concepts such as dependency injection, service patterns, and the repository pattern, while also highlighting improvements made in code maintainability and testing through a revised approach. The document includes examples of code implementations and offers links to the associated GitHub repository.
![Let’s consider a scenario !
1. Design and develop an API to
a. Create User
i. Stores user in mysql database
ii. Store user information in cache
iii. Stores user profile in mixpanel (This tool can be changed in future)
b. Get User
i. Gets User Information from cache
ii. If not present in cache, get from database
2. User has following properties
a. id (integer)
b. name (string)
c. email (string)
d. subscription (Subscription) [has One]
e. role (Role) [has One]](https://image.slidesharecdn.com/developingcleanservicesusinglaravel-201218063527/85/Developing-clean-services-using-laravel-8-320.jpg)
Developing clean services using laravel
- 1. Topics Covered: 1. What is laravel. 2. Understanding Application life cycle with laravel. 3. Understanding Classes & their communication! 4. Discussing a scenario, and implementing it (v1). 5. Understanding some important concepts. 6. Implementing it with new concepts (v2). 7. Q / A
- 2. 1. What is laravel ? 1. Laravel is a free, open-source PHP web framework, created by Taylor Otwell and intended for the development of web applications following the model–view–controller architectural pattern and based on Symfony 2. It is a full stack framework AND also API framework as well 3. We’ll focus our discussion considering it as a API framework, i.e. excluding Sessions, Views, etc. 4. We’ll be more focused on discussing patterns that improve our daily application development process.
- 4. So many buzzwords ! - Service Provider - Service Container - Dependency Injection - SOLID - IoC - Middleware - etc
- 5. It’s all about Classes & their communication ! Object Graph ! ->
- 6. Let’s divide Classes into two categories ! 1. Entities / Models a. Hold attributes / properties, with setters / getters b. Can have multiple objects, can be instantiated multiple times in a Request life cycle c. E.g. Car, Engine, Seat, etc. d. Can be dependent on other Models 2. Services a. Holds behavior b. Mostly likely instantiated once in Application life cycle c. E.g. CreateCarService, GetAllCars etc d. Can be dependent on other Services / Models e. Can be Singleton
- 8. Let’s consider a scenario ! 1. Design and develop an API to a. Create User i. Stores user in mysql database ii. Store user information in cache iii. Stores user profile in mixpanel (This tool can be changed in future) b. Get User i. Gets User Information from cache ii. If not present in cache, get from database 2. User has following properties a. id (integer) b. name (string) c. email (string) d. subscription (Subscription) [has One] e. role (Role) [has One]
- 9. Implementation # 1 : 1. No separation of concerns 2. No services 3. No dependency injection 4. No Repositories 5. No use of Service Container 6. Can’t write unit tests 7. Not maintainable code ! Code available : https://github.com/khatritariq/laravel-clean-services (v1 routes)
- 10. Let’s solve these problems within same system, and address them one by one ! But we need to understand few concepts before ! 1. Dependency Injection (SOLID) 2. Single Responsibility principle (SOLID) by using ADR pattern 3. DRY (Don’t Repeat Yourself) 4. Service Pattern 5. Service Container / Service Provider 6. Repository Pattern
- 12. Dependency Injection in Services
- 13. Single Responsibility Principle 1. Use of ADR pattern a. Single Controller (per action) 2. Controller to only be responsible for Input Validation and Transfer control to Service 3. Single Service Class 4. A class should have only one reason to change
- 14. DRY (Don’t Repeat Yourself) - With introduction of Services, we don’t have to repeat the Controller Code into Commands, if the same program has to be executed via CLI - Services help us not Repeat the same program at multiple places
- 15. Service / Service Container / Service Provider
- 16. Service Container Service Container: The Laravel service container is a powerful tool for managing class dependencies and performing dependency injection.
- 17. Service Provider Service providers are the central place of all Laravel application bootstrapping. Your own application, as well as all of Laravel's core services are bootstrapped via service providers.
- 18. Repository Pattern Repository encapsulates methods that persist and retrieve your business data with some kind of storage (e.g.: a database, cache, etc). Also generally we create a Repository to each entity (model).
- 20. Implementation # 2: 1. No separation of concerns (Addressed via ADR / Services) 2. No services (Addressed) 3. No dependency injection (Addressed) 4. No Repositories (Addressed) 5. No use of Service Container (Addressed) 6. Can’t write unit tests (Addressed) 7. Not maintainable code ! (Addressed) Code available : https://github.com/khatritariq/laravel-clean-services (v2 routes)
- 21. Questions ?
- 22. Thank you !