Repository design pattern in laravel

Jul 19, 2015Download as pptx, pdf2 likes918 views

This document discusses the repository design pattern in Laravel. It explains that the repository pattern adds a service layer between the controller and database to abstract away data access logic. This makes the code more organized, testable, and adaptable to different databases. It provides an example of implementing a common repository interface with an Eloquent repository class to retrieve contact data for a controller. The key benefit highlighted is that switching databases is simply a matter of binding a different repository implementation.

Repository Design
Pattern in Laravel
Samir Poudel

The elements of this language are entities called patterns. Each pattern describes
a problem that occurs over and over again in our environment, and then
describes the core of the solution to that problem, in such a way that you can use
this solution a million times over, without ever doing it the same way twice.
— Christopher Alexander

Design Patterns
1. Builder
2. Chain of responsibility
3. Command
4. Facade
5. Factory
6. Iterator
7. Mediator
8. Observer
9. Presenter
10.Repository
11.Singleton
12.Strategy

LARAVEL is always awesome to
use. So why to use these design
patterns ?

class CommonController extends
BaseController
{
public function all()
{
$contacts = Contacts:all();
return
View::make(‘contacts.all’,
compact($contacts));
}
}
So it’s the way right ?
Common Controller
1. Tied to eloquent.
2. Not easily testable.
3. Maintenance is tough.
4. Bugs.
5. bla bla bla bla

Repositories
1. Repository design pattern is actually simple. Its just the addition of another
layer into your system. The Service Layer.
2. By this you add another layer to communicate with your database and
other thing instead of controller.
3. No need to write multiple codes.
4. Easily changeable DB.
5. Less headache.

What’s a repository
class CommonRepository
{
public function all()
{
return Contacts::all();
}
}

Repository Controller
class CommonController extends BaseController
{
public function all()
{
$contactsRepo = new ContactRepository();
$contacts = $contactsRepo->all();
return View::make(‘contacts.list’, compact($contacts));
}
}

Project Structure
- app
-- lib
--- Repository
---- Storage
----- Common
Interface Class : CommonRepository.php
Eloquent Class Implemented from interface : EloquentCommonRepository.php

Creating the service provider to bind two repositories together
<?php namespace RepositoryStorage;
use IlluminateSupportServiceProvider;
class StorageServiceProvider extends ServiceProvider
{
public function register() {
$this->app->bind( RepositoryStorageUserCommonRepository,
RepositoryStorageCommonEloquentCommonRepository );
}
}
Finally in the providers listing you need to add it
'providers' => array( // -- RepositoryStorageStorageServiceProvider' ),

$Implementation <?php use RepositoryStorageCommonCommonRepository as Common; class CommonController extends BaseController { public function __construct(Common $common) { $this->common = $common; } public function index() { return $this->common->function(); } }$

What if we change DB ?
Switching to any new database or any changes are simple now.
$this->app->bind( ‘RepositoryStorageCommonCommonRepository',
‘RepositoryStorageCommonMongoCommonRepository' );

I don’t have more to say ;)
Ways to connect with me
@samirpdl
www.samirpdl.com.np
samir@samirpdl.com.np

Over the last year there has been a lot of buzz about Clean Architecture in the Android community, but what is Clean Architecture? How does it work? And should I be using it? Recently at Badoo we decided to rewrite our messenger component. Over the years this core piece of functionality in our app has become large and unwieldy. We wanted to take a fresh approach to try and prevent this from happening again. We choose to use Clean Architecture to achieve our goal. This talk intends to share our journey from theory to implementation in an application with over 100 million downloads. By the end, you should not only understand what Clean Architecture is, but how to implement it, and whether you should.

Introducing Clean ArchitectureRoc Boronat

Asp.Net Core MVC with Entity FrameworkShravan A

This document provides an overview of ASP.Net Core MVC with Entity Framework. It discusses ASP.Net Core as an open source and cross-platform framework for building web applications. It also describes MVC architecture, Entity Framework as an ORM tool, the repository pattern, and using a database first approach. The document includes sections on requirements, advantages of ASP.Net Core, and concludes that it allows for improved performance, cross-platform support, less code, and easier maintenance of web applications.

ElasticsearchShagun Rathore

This slide deck talks about Elasticsearch and its features. When you talk about ELK stack it just means you are talking about Elasticsearch, Logstash, and Kibana. But when you talk about Elastic stack, other components such as Beats, X-Pack are also included with it. what is the ELK Stack? ELK vs Elastic stack What is Elasticsearch used for? How does Elasticsearch work? What is an Elasticsearch index? Shards Replicas Nodes Clusters What programming languages does Elasticsearch support? Amazon Elasticsearch, its use cases and benefits

Azure Functions & Serverless ComputingAbhimanyu Singhal

Azure Functions allow developers to create event-driven, serverless applications on Azure. Functions can be triggered by events from other Azure services, third party services, or on-premises systems. They are designed to operate at a small scale and only when needed, making them cost-effective. Functions support languages like C#, JavaScript, Python and more. Common uses include web jobs, processing data from queues and containers, and building APIs with HTTP triggers.

Introduction to RedisArnab Mitra

Redis is an open source, in-memory data structure store that can be used as a database, cache, or message broker. It supports data structures like strings, hashes, lists, sets, sorted sets with ranges and pagination. Redis provides high performance due to its in-memory storage and support for different persistence options like snapshots and append-only files. It uses client/server architecture and supports master-slave replication, partitioning, and failover. Redis is useful for caching, queues, and other transient or non-critical data.

Microservices Docker Kubernetes Istio Kanban DevOps SREAraf Karsh Hamid

Introduction to Microservices Architecture, Docker, Kubernetes, Istio, Testing Strategies for Microservices based Apps. Security Best Practices. Kanban, DevOps, and SRE. Infrastructure Design Patterns - API Gateway - Service Discovery - Load Balancer - Circuit Breaker - Let-it-Crash Pattern Software Design Patterns - Hexagonal Architecture - Domain Driven Design - Event Sourcing and CQRS - Functional Reactive Programming

Documenting your REST API with Swagger - JOIN 2014JWORKS powered by Ordina

Swagger is a specification and complete framework implementation for describing, producing, consuming, and visualizing RESTful web services. The overarching goal of Swagger is to enable client and documentation systems to update at the same pace as the server. The documentation of methods, parameters, and models are tightly integrated into the server code, allowing APIs to always stay in sync. With Swagger, deploying managing, and using powerful APIs has never been easier.

[Webinar]: Working with Reactive SpringKnoldus Inc.

Clean architectureLieven Doclo

Lieven DOCLO gave a presentation on implementing Clean Architecture. Clean Architecture advocates separating domains, applications, and interfaces into separate layers. This allows the inner layers to be independent of the outer layers and frameworks. The presentation demonstrated creating building-related use cases and domain models, implementing repositories, and exposing use cases through REST endpoints. It discussed issues like decoupling tradeoffs, pragmatic compromises, and applying Clean Architecture to legacy projects.

CI/CD OverviewAn Nguyen

This document provides an overview of continuous integration (CI), continuous delivery (CD), and continuous deployment. CI involves regularly integrating code changes into a central repository and running automated tests. CD builds on CI by automatically preparing code changes for release to testing environments. Continuous deployment further automates the release of changes to production without human intervention if tests pass. The benefits of CI/CD include higher quality, lower costs, faster delivery, and happier teams. Popular CI tools include Jenkins, Bamboo, CircleCI, and Travis. Key practices involve automating all stages, keeping environments consistent, and making the pipeline fast. Challenges include requiring organizational changes and technical knowledge to automate the full process.

Understanding MicroSERVICE Architecture with Java & Spring BootKashif Ali Siddiqui

Spring data jpaJeevesh Pandey

Introducing SwaggerTony Tam

Clean ArchitectureZahra Heydari

Introduction to CI/CDSteve Mactaggart

Getting Started with Azure ArtifactsCallon Campbell

Spring Data JPAKnoldus Inc.

Kubernetes #1 introTerry Cho

Kubernetes is an open-source container management platform. It has a master-node architecture with control plane components like the API server on the master and node components like kubelet and kube-proxy on nodes. Kubernetes uses pods as the basic building block, which can contain one or more containers. Services provide discovery and load balancing for pods. Deployments manage pods and replicasets and provide declarative updates. Key concepts include volumes for persistent storage, namespaces for tenant isolation, labels for object tagging, and selector matching.

Introduction to RedisDvir Volk

Azure DevOpsJuan Fabian

This document provides information about Azure DevOps and DevOps practices. It discusses how DevOps brings together people, processes, and technology to automate software delivery and provide continuous value to users. It also outlines some key DevOps technologies like continuous integration, continuous delivery, and continuous monitoring. Additionally, the document shares how Azure DevOps can help teams deliver software faster and more reliably through tools for planning, source control, building, testing, and deploying.

Introducing type scriptRemo Jansen

TypeScript is a typed superset of JavaScript that compiles to plain JavaScript. It allows for large scale JavaScript application development with features like classes, inheritance, modules, generators, async/await, and decorators. TypeScript introduces strong typing, interfaces, generics, and other design-time features not available in JavaScript to reduce complexity in large codebases. It supports the future of JavaScript by allowing the use of ES6 and ES7 features today through compiler options. Getting started is easy using the TypeScript playground or boilerplate projects on GitHub.

API for BeginnersGustavo De Vita

This document provides an overview of APIs and how they work. It begins with basic API concepts and definitions, then demonstrates how APIs are used by having programs interact with applications to access structured data without direct human interaction. It provides examples of common API uses for maps, login/authentication, payments, messaging and more. It also introduces the concept of webhooks which allow applications to "call" other services when data is available, rather than requiring the other service to periodically check via API calls. Overall it serves as a high-level introduction to APIs and webhooks for beginners.

Stream processing using KafkaKnoldus Inc.

Clean architecture.NET Crowd

The document discusses the principles of clean architecture. It states that clean architecture aims to minimize human effort required to build and maintain software systems. It emphasizes that the core of an application should be its use cases rather than technical details like databases or frameworks. The architecture should clearly communicate the intent of the system. It also notes that dependencies should flow inward from outer layers like interfaces to inner layers containing core business logic and entities.

Best practices tekxLorna Mitchell

The document discusses several software development best practices including source control, coding standards, design patterns, documentation, testing, and deployment. It provides examples and explanations of common design patterns like factory, registry, adapter, decorator, and observer. Resources for further information on topics like Subversion, Git, coding standards, and design patterns are also referenced.

Java 8 OverviewNicola Pedot

This document provides an overview of Java 8 including: - Java 8 has approximately 9 million developers and Oracle supports versions 6-8. - New features include default methods, lambda expressions, streams, and parallel processing capabilities. - JavaScript integration allows JavaScript code to be run from Java, enabling database and other connections from JavaScript. - Potential issues with Java 8 include more complex debugging due to lambda expressions and increased abstraction.

More Related Content

What's hot (20)

Introduction to RedisArnab Mitra

Microservices Docker Kubernetes Istio Kanban DevOps SREAraf Karsh Hamid

Documenting your REST API with Swagger - JOIN 2014JWORKS powered by Ordina

[Webinar]: Working with Reactive SpringKnoldus Inc.

Clean architectureLieven Doclo

CI/CD OverviewAn Nguyen

Understanding MicroSERVICE Architecture with Java & Spring BootKashif Ali Siddiqui

Spring data jpaJeevesh Pandey

Introducing SwaggerTony Tam

Clean ArchitectureZahra Heydari

Introduction to CI/CDSteve Mactaggart

Getting Started with Azure ArtifactsCallon Campbell

Spring Data JPAKnoldus Inc.

Kubernetes #1 introTerry Cho

Introduction to RedisDvir Volk

Azure DevOpsJuan Fabian

Introducing type scriptRemo Jansen

API for BeginnersGustavo De Vita

Stream processing using KafkaKnoldus Inc.

Clean architecture.NET Crowd

Introduction to RedisArnab Mitra

Microservices Docker Kubernetes Istio Kanban DevOps SREAraf Karsh Hamid

Documenting your REST API with Swagger - JOIN 2014JWORKS powered by Ordina

[Webinar]: Working with Reactive SpringKnoldus Inc.

Clean architectureLieven Doclo

CI/CD OverviewAn Nguyen

Understanding MicroSERVICE Architecture with Java & Spring BootKashif Ali Siddiqui

Spring data jpaJeevesh Pandey

Introducing SwaggerTony Tam

Clean ArchitectureZahra Heydari

Introduction to CI/CDSteve Mactaggart

Getting Started with Azure ArtifactsCallon Campbell

Spring Data JPAKnoldus Inc.

Kubernetes #1 introTerry Cho

Introduction to RedisDvir Volk

Azure DevOpsJuan Fabian

Introducing type scriptRemo Jansen

API for BeginnersGustavo De Vita

Stream processing using KafkaKnoldus Inc.

Clean architecture.NET Crowd

Similar to Repository design pattern in laravel (20)

Best practices tekxLorna Mitchell

Java 8 OverviewNicola Pedot

Why Laravel?Jonathan Goode

This document provides an overview of the Laravel PHP framework. It discusses Laravel's history and evolution from version 1 to the current version 5.3. Key Laravel concepts are explained such as routing, controllers, models, views, Artisan commands, and architectural changes in version 5 like the directory structure and environment detection. Additional Laravel tools and resources are also mentioned like Laravel Elixir, Homestead, and Laracasts.

Make your application expressiveChristian Varela

Osiąganie mądrej architektury z Symfony2 3camp

Wojciech Sznapka presents key principles for achieving wise architecture with Symfony2: 1. Follow SOLID principles - each component should have a single responsibility and dependencies should be injected through interfaces. 2. Prioritize maintainability - thoroughly test code and implement logging. 3. Design for scalability - avoid dependencies on local storage, scale the database, and optimize for horizontal scaling. Wise architecture is achieved by following best practices, leveraging existing bundles, and ensuring the application can be easily maintained and scaled over time.

Rupicon 2014 Action packrupicon

ActionPack is a Rails framework that handles web requests and responses. It consists of Action Controller, which performs request logic and fetches/saves data from models, and Action View, which renders templates using views. Action Controller uses conventions to handle requests and provides parameters, filters, flashes, and variants to manage requests and responses. Action View renders templates using helpers and can be used independently of Active Record.

Features java9srmohan06

Ruby On RailsBalint Erdi

Ruby on Rails is a web application framework written in Ruby that emphasizes convention over configuration and rapid development. It includes modules for modeling data with ActiveRecord, handling requests and responses with ActionController and ActionView, and additional features like routing and internationalization. The document then provides more details on the history, philosophy, main components, and features of Rails.

C# c# for beginners crash course master c# programming fast and easy todayAfonso Macedo

The document provides an overview and table of contents for a book on learning C# programming for beginners. It covers 14 chapters that introduce C# concepts like program structure, syntax, data types, variables, operators, decision making statements, loops, classes, methods, arrays, strings, encapsulation, inheritance, interfaces, exception handling, and multithreading. The book is aimed at helping readers master C# programming quickly and easily through explanations and examples in each chapter.

Advanced Interfaces and Repositories in LaravelJonathan Behr

This document discusses best practices for organizing code in a maintainable way using interfaces, repositories, and dependency injection. It advocates separating code from the database layer by using repositories to act as a service layer between the application and database. Repositories follow contracts defined by interfaces rather than directly using models. This loosens coupling and allows more flexibility. The document provides examples of implementing repositories, interfaces, dependency injection, multi-tenant support, and an admin resource controller to demonstrate these concepts.

Content Staging in Drupal 8Dick Olsson

Drupal 8 has made significant improvements towards the ability to stage configuration. But what about content staging? Has it gotten easier in Drupal 8? This session is targeted towards site builders where we will continue to explore the content staging solution that is being built for Drupal 8 and that was initially presented in Austin. It's a solution that brings vast improvements to sites owners that need to stage or replicate content across sites. Further, site builders will learn how this solution also applies to broader and sometimes more exciting use cases - content sharing and filtered replication across networks of sites and applications. The recorded video is available here: https://amsterdam2014.drupal.org/session/content-staging-drupal-8-continued

What is DDD and how could it help youLuis Henrique Mulinari

Domain-driven design (DDD) is a software development approach that focuses on the core domain and business logic. It proposes a ubiquitous language between business experts and developers. DDD is useful for complex domains with many business rules and an iterative development process. It aims to produce software that is flexible, extensible and has testable code agreed upon by domain experts and developers. Key aspects of DDD include modeling the domain using entities, value objects, aggregates and repositories. Other patterns like factories, services and commands can also be used. CQRS separates reads from writes for flexibility and performance. Frameworks like ORM, dependency injection and UUIDs can help implement DDD in PHP applications.

Intro to Rails 4Kartik Sahoo

This document provides an introduction and overview of key changes between Rails 3 and Rails 4. It discusses changes to components like ActiveRecord and ActionPack. It outlines changes to models, including the introduction of AREL and concerns directories. Controller changes like strong parameters and view changes like new form helpers are reviewed. Routing changes such as PATCH verbs and constraints are covered. Finally, migration and turbolinks additions are summarized.

Código Saudável => Programador Feliz - Rs on Rails 2010Plataformatec

React Native +Redux + ES6 (Updated)Chiew Carol

This document provides an overview of React Native, Redux, and ES6 concepts. It begins with an introduction to React Native fundamentals like components, props vs state, and styling. It then covers Redux terminology such as actions, reducers, and middleware. Finally, it discusses ES6 features like arrow functions, destructuring, and template literals. Code examples and links to documentation are provided throughout for illustrating key concepts.

Modular programming Using Object in ScalaKnoldus Inc.

Scala is a scalable language is that we can use the same techniques to construct small as well as large programs. In this presentation we’ve focused primarily on programming in the small: designing and implementing the smaller program pieces out of which we can construct a larger program.The other side of the story is programming in the large: organizing and assembling the smaller pieces into larger programs, applications, or systems.

Repository Pattern in MVC3 Application with Entity FrameworkAkhil Mittal

The document discusses implementing a repository pattern in an MVC application using Entity Framework. It begins with an introduction and roadmap of previous articles. It then discusses the benefits of a repository pattern in abstracting the data access layer from business logic. Steps are provided to create a sample repository interface and class to implement basic CRUD operations on a User entity, abstracting the data access code from the controller. The repository class uses the Entity Framework context to perform operations while resolving tight coupling issues between layers. It concludes that while this implementation works for a single entity, a generic repository will be needed to cleanly support multiple entities without duplication.

Beyond MVC: from Model to DomainJeremy Cook

The document discusses different software architectural patterns for managing complexity in web applications. It begins by explaining model-view-controller (MVC) and some of its limitations. It then introduces Action Domain Responder (ADR) as a refinement of MVC that maps more closely to the lifecycle of a web request. Next, it covers hexagonal architecture, also known as ports and adapters, which isolates an application from its inputs and outputs. Finally, it provides an overview of domain-driven design (DDD), including architectural patterns like bounded contexts and object patterns like entities, value objects, domain services, aggregates, and repositories.

Lambdas & StreamsC4Media

Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/1eZv11J. Simon Ritter discusses the syntax and use of Lambda expressions, focusing on using Streams to greatly simplify the way bulk and aggregate operations are handled in Java. Filmed at qconlondon.com. Simon Ritter is a Java Technology Evangelist at Oracle Corporation. Simon has been in the IT business since 1984 and holds a Bachelor of Science degree in Physics from Brunel University in the U.K.

Nt1310 Unit 3 Language AnalysisNicole Gomez

This document discusses an automatic code generation tool called UJECTOR that can generate executable Java code from UML diagrams, including class diagrams, sequence diagrams, and activity diagrams. It notes the benefits of automatic code generation in reducing errors compared to manual coding. The paper also discusses some related work, including Enterprise Architect, Eclipse UML Generators, Rhapsody, and dCode - other tools that can generate code from UML models. Overall, the document examines challenges in ensuring consistency, accuracy, maintainability and efficiency when automatically generating code from UML models.

Best practices tekxLorna Mitchell

Java 8 OverviewNicola Pedot

Why Laravel?Jonathan Goode

Make your application expressiveChristian Varela

Osiąganie mądrej architektury z Symfony2 3camp

Rupicon 2014 Action packrupicon

Features java9srmohan06

Ruby On RailsBalint Erdi

C# c# for beginners crash course master c# programming fast and easy todayAfonso Macedo

Advanced Interfaces and Repositories in LaravelJonathan Behr

Content Staging in Drupal 8Dick Olsson

What is DDD and how could it help youLuis Henrique Mulinari

Intro to Rails 4Kartik Sahoo

Código Saudável => Programador Feliz - Rs on Rails 2010Plataformatec

React Native +Redux + ES6 (Updated)Chiew Carol

Modular programming Using Object in ScalaKnoldus Inc.

Repository Pattern in MVC3 Application with Entity FrameworkAkhil Mittal

Beyond MVC: from Model to DomainJeremy Cook

Lambdas & StreamsC4Media

Nt1310 Unit 3 Language AnalysisNicole Gomez

Repository design pattern in laravel

1. Repository Design Pattern in Laravel Samir Poudel

2. The elements of this language are entities called patterns. Each pattern describes a problem that occurs over and over again in our environment, and then describes the core of the solution to that problem, in such a way that you can use this solution a million times over, without ever doing it the same way twice. — Christopher Alexander

3. Design Patterns 1. Builder 2. Chain of responsibility 3. Command 4. Facade 5. Factory 6. Iterator 7. Mediator 8. Observer 9. Presenter 10.Repository 11.Singleton 12.Strategy

4. LARAVEL is always awesome to use. So why to use these design patterns ?

5. Repository Design Pattern

6. class CommonController extends BaseController { public function all() { $contacts = Contacts:all(); return View::make(‘contacts.all’, compact($contacts)); } } So it’s the way right ? Common Controller 1. Tied to eloquent. 2. Not easily testable. 3. Maintenance is tough. 4. Bugs. 5. bla bla bla bla

7. Now what ??

8. Repositories 1. Repository design pattern is actually simple. Its just the addition of another layer into your system. The Service Layer. 2. By this you add another layer to communicate with your database and other thing instead of controller. 3. No need to write multiple codes. 4. Easily changeable DB. 5. Less headache.

9. What’s a repository class CommonRepository { public function all() { return Contacts::all(); } }

10. Repository Controller class CommonController extends BaseController { public function all() { $contactsRepo = new ContactRepository(); $contacts = $contactsRepo->all(); return View::make(‘contacts.list’, compact($contacts)); } }

11. Project Structure - app -- lib --- Repository ---- Storage ----- Common Interface Class : CommonRepository.php Eloquent Class Implemented from interface : EloquentCommonRepository.php

12. Creating the service provider to bind two repositories together <?php namespace RepositoryStorage; use IlluminateSupportServiceProvider; class StorageServiceProvider extends ServiceProvider { public function register() { $this->app->bind( RepositoryStorageUserCommonRepository, RepositoryStorageCommonEloquentCommonRepository ); } } Finally in the providers listing you need to add it 'providers' => array( // -- RepositoryStorageStorageServiceProvider' ),

13. Implementation <?php use RepositoryStorageCommonCommonRepository as Common; class CommonController extends BaseController { public function __construct(Common $common) { $this->common = $common; } public function index() { return $this->common->function(); } }

14. What if we change DB ? Switching to any new database or any changes are simple now. $this->app->bind( ‘RepositoryStorageCommonCommonRepository', ‘RepositoryStorageCommonMongoCommonRepository' );

15. I don’t have more to say ;) Ways to connect with me @samirpdl www.samirpdl.com.np [email protected]

Repository design pattern in laravel

Recommended

More Related Content

What's hot (20)

Similar to Repository design pattern in laravel (20)

Repository design pattern in laravel