I am finishing up a large project using Laravel 4 and had to answer all of the questions you are asking right now. After reading all of the available Laravel books over at Leanpub, and tons of Googling, I came up with the following structure. One Eloquent Model class per datable table One Repository class per Eloquent Model A Service class that may communicate between multiple Repository classes.
If i'm using soft delete in laravel 4.2 (database is mysql), every eloquent query has WHERE deleted_at IS NULL. There are no indexes on deleted_at. Will it be slow on big tables? (or maybe IS NULL is optimized without needing an index) Should I add an index on the deleted_at column? So, does Laravel's "soft_delete" deleted_at column need an index in MySQL? Clarification: Laravel stores a timestamp
Highly modular Framework design Laravel Zero is a lightweight and modular micro-framework for developing fast and powerful console applications. Built on top of the Laravel components. Write powerful Console applications Laravel Zero has a simple and powerful syntax that enables developers to build very complex applications far more quickly than with any previous framework. For Artisans 100% Open
A simple architecture is perfect for a simple application. But, as the application grows in its complexity, the architecture must become more complex in order to prevent it from becoming unmaintainable. In this talk we discuss some ideas for simplifying complex code bases. We also discuss the important distinctions between presentation, service, and domain layers and strategies for separating high
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く