実際、RailsのブートシーケンスとかもCakePHP使ってた感覚で探り当てられたみたいなのはある(とはいえ細かいところを確認するためにRailsのソースコードまで読みに行く羽目になったけど)
18
今は違うけど、元々CakePHPはPHP版Railsクローンってくらい酷似してたってのと、大枠はそこまで変わらんよねっていうのでCakePHPを使ってる身としてはRailsの仕組みや挙動なんかは感覚でこんな感じかな？って肌感で読めるみたいなのはある
17
Updated Post: CakePHP vs CodeIgniter: Which PHP Framework is Best for Development?
#Guides #WebHosting
blog.radwebhosting.com/cakep…
ALT CakePHP vs CodeIgniter: Which PHP Framework is Best for Development?
1
Bimal Patel retweeted
Need a fast, secure, and scalable web solution?
Fast-track your project with reliable CakePHP development tailored to your business goals.
Explore: myratechnolabs.com/cakephp-d…
#CakePHP #WebDevelopment #CustomSoftware #TechSolutions #DigitalTransformation
1
1
5
The whole point of the data liberation project is that you can easily come and go. I had a multi-year affair with Drupal, a tryst with Squarespace, a brief fling with CakePHP, one night in Joomla… Go have fun. We know you’ll be back. 😉
wordpress.org/data-liberatio…
1
90
柴田 怜（しばた・さとる） retweeted
①7月or8月〜TypeScript/JavaScript(jQuery)/React(Next.js)/Vue.js(Nuxt2/3)/週2リモート
②即日〜/PHP (Laravel, CakePHP, Symfony, ZendFW, Smarty/フルリモート
③7月〜/PMO/企画業務/社内SE/ヘルプデスク/常駐可能
④7月〜/TypeScript/JavaScript/Python/フルリモ希望
#SES #要員紹介 #TypeScript #PHP #PMO
1
1
214
Nice article!
This pattern was inspired by the entity pattern used in CakePHP.
36
Jun 8
Codeigniter,
Yii
CakePHP,
Magento,
Slim
Wiki
PHP has set the era of Web Development!
1
3
149
Jun 6
#CakePHP plays well together with #PHPStan and #Psalm. From core to ORM and to all parts of the framework.
And now even on the generics part:
dereuromark.de/2026/06/06/ca…
2
53
the INEC portal was built with CakePHP, an outdated php framework 😭😭, I last used cakephp 7 years ago. The worse part is there is no error handling you can literally see everything. We are fuxked
1
1
8
558
Ｑ：30歳・バックエンドエンジニア4年目で、現在転職活動中です。技術スタックは PHP / Laravel / CakePHP / TypeScript が中心です。学歴や職歴は一般的なキャリアルートではなく、英語での業務経験もほぼありません。強みは、現場理解、コードリーディング、SQL調査、仕様整理、業務改善、作る／作らない判断です。ドキュメントや有識者が少ない環境で、コードやデータから仕様を再構築し、業務改善やシステム改善を進めてきました。一方で、アーキテクチャ設計、技術選定、DDD、Clean Architecture、レイヤードアーキテクチャなどの体系知識には課題があります。今後、まずは年収1000万円を目指したいです。この場合、いきなり外資系や高年収企業を狙うよりも、まずはレビュー文化や設計議論が強い会社で2〜3年ほど技術判断力・設計力・モダンな開発経験を積み、その後に外資系や高年収企業を目指す方が現実的でしょうか？また、私のように「業務理解・仕様整理・課題解決」には強みがある一方で、「技術体系」に課題があるバックエンドエンジニアが、1000万円を目指すために優先して伸ばすべきスキルや、選ぶべき会社の特徴があれば教えていただきたいです。
酒井潤の回答はこちら↓
ask.alamoa.io/q/wzn1g52 #AskJun #酒井潤 #エンジニア #キャリア
7
2,385
Thank you so much, man! 🫶
I'll read the article now, but the funny thing is that CakePHP was the first PHP framework I used for quite some time, and this package had some inspiration by it!
1
2
312
Jun 3
Over the years of being a developer I've been fortunate enough to get to use a number of different frameworks to build applications with.
I remember when I first started to use CakePHP and it baffled me that there were two separate files for the same database table you had a Table class and a Entity class for instance PostsTable and Post entity. After A while of using the framework it made sense to me.
The table handles database behaviour - querying, associations, persistence. The entity handles your data - its shape, its rules, its logic as a PHP object. They're different responsibilities, even when they touch the same table.
Since moving to Laravel I've thought about this separation a lot. Eloquent is brilliant - I'm not changing my view on that. But passing models through every layer of an application creates problems that compound:
→ Any layer can call save() by accident
→ No real type safety - magic __get() all the way down
→ Services become Eloquent-coupled and painful to unit test
→ Database column names leak into your domain logic
At @jumptwenty4 we've used DTOs for the input side for years packages like @spatie_be Laravel Data really helped with this.
A recently released package by @wendell_adriel called Laravel Expressive landed this week. It instantly reminded me of the CakePHP Entity pattern but done for Laravel
One trait on your model. One Artisan command. Your services and actions receive typed PHP objects - public, typed properties, proper enums, no Eloquent magic.
The bit that surprised me: what it does for testing. Once your services accept Expressive objects, unit tests mean constructing a plain PHP object. No database. No factories. No mocking Eloquent.
I've written a breakdown on the Jump24 journal - code examples, Pest testing patterns and an honest look at every limitation worth knowing before you adopt:
jump24.co.uk/journal/laravel…
Big thanks to Wendell Adriel once again for all the work he's put in for this new package.
1
3
8
1,041
