Laravel: Repository Pattern in practice

Рет қаралды 10,717

Күн бұрын

Hi guys!
In this video series, I'll be showcasing a simple way to integrate repository pattern into your Laravel application. We'll start with a super simple example - an app that stores blog posts.
Chapters
00:00 - Introduction & Simple Blog Post
06:12 - Why would you use it
07:24 - Implementation
26:05 - Wrap up
For more content visit saaslaravel.com

Пікірлер: 22

@verard0 Жыл бұрын

really nice video! you covered a lot of info! congrats for your work!

@rahmaabdelaziz4095 Жыл бұрын

great work

@Muhammed-nani964 11 ай бұрын

I think service (action) + DTO is better you may want to create a video on it

@mohammadjavadrajabloo2711 Ай бұрын

Good Video!

@user-ou5gg7pv4m 10 ай бұрын

Hello we made injection on BaseRepository for Model but ı did same things laravel give an error like " Target [Illuminate\Database\Eloquent\Model] is not instantiable while building [App\Http\Controllers\BlogController, App\Repositories\BlogRepository]" when ı make like " $this->app->bind(BlogRepositoryInterface::class,BlogRepository::class);" in AppServiceProvider for solition ı changed this as " $this->app->bind(BlogRepositoryInterface::class,function (){ return new BlogRepository(new Blog()); });" is there any solution ? Thank you for feeds from now ...

@GergelyCsermely 11 ай бұрын

Hi! I would suggest to use Route::resource

@saaslaravel 11 ай бұрын

Never. I hate those! They decrease visibility for me

@parumhr1268 9 ай бұрын

what are the advantages to implementing the BlogRepositoryInterface as to just injecting the BlogRepository directly in the constructor??

@saaslaravel 9 ай бұрын

You have the freedom to change the implementation of the repository i.e you can change persistence layer or move it to a 3rd party without changing how it interacts with the rest of the application

@user-fx1qh8ml5v 5 ай бұрын

Its better to use BlogPost::query()->toBase()->first() instead of BlogPost::first()->toArray(), because in second scenario, laravel convert array from DB to Eloquent, and convert eloquent to array. In first scenario you get raw data without converting

@alexz75515 Жыл бұрын

Because this line is very long you can tell that this is an enterprise application... 😆

@himasami2200 Жыл бұрын

can u please give me a source code of this video to study?

@saaslaravel Жыл бұрын

I don't have source code for it unfortunately. Will be doing that for any videos going forward 😄

@DailyTechShot 4 ай бұрын

Please people, do not use a repository pattern in Laravel. Laravel has a beautiful active record solution and a repository pattern would only make sense when you would actually want to swap your database implementation, from let's say Mysql to Mongo for example. Do not use 'patterns' for the sake of using them. .

@hydrokat143 2 ай бұрын

eloquent can switch over databases with some config changes in the database config and/or eloquent model. question is… is switching from sql to nosql or vv a thing?

@topvova Жыл бұрын

Why add an extra layer to Eloquent with interfaces and DTOs? This approach only clutters the code and reduces its maintainability.

@saaslaravel Жыл бұрын

I never use it personally but some of the reasons include decoupling the entity model from the database or organisation and reuse of more complex queries

@impulserr 5 ай бұрын

You can mock it easier for tests and it is cleaner imo. I like repositories for readonly eloquent/queries and services on top of that only if I need some more processing/logic + jobs if u need to update/insert/delete. Personally I think it is much better then throwing all to services.

@user-uh6qn1ef1d 2 ай бұрын

I personally do controller