The Backend For Frontend Pattern
– Edit
Mohamed Said explains an interesting pattern for you to consider that can potentially make authenicating from the frontend easier.
All my posts about architecture.
– Edit
Mohamed Said explains an interesting pattern for you to consider that can potentially make authenicating from the frontend easier.
by Freek Van der Herten – 9 minute read – Edit
Today we released a package to make Laravel apps tenant aware, called laravel-multitenancy. The philosophy of this package is that it should only provide the bare essentials to enable multitenancy.
The package can determine which tenant should be the current tenant for the request. It also allows you to define what should happen when switching the current tenant to another one.
It works for multitenancy projects that need to use one or multiple databases.
In this blog post, I'd like to introduce the package to you.
Join 9,500+ smart developers
Get my monthly newsletter with what I learn from running Spatie, building Oh Dear, and maintaining 300+ open source packages. Practical takes on Laravel, PHP, and AI that you can actually use.
No spam. Unsubscribe anytime. You can also follow me on X.
"As a Laravel developer, this is the one newsletter I most look forward to. Freek has a talent for distilling packages or techniques down to something immediately useful - one tip can save you hours and even weeks. It's concise and practical and highly relevant."
What's the ideal amount of abstraction? When does a framework start having "too much magic"? When are there too many languages in an organisation?
Read more [ferd.ca]
– Edit
In this video, Mohammed Said shares a nice, clean strategy for multitenancy in Laravel.
– stitcher.io - submitted by Brent – Edit
In this two-part series, my colleague Freek and I will discuss the architecture of a project we're working on.
Read more [stitcher.io]
by Freek Van der Herten – 10 minute read – Edit
– stitcher.io – Edit
Brent did a cool experiment with ReactPHP and event sourcing.
Read more [stitcher.io]
by Freek Van der Herten – 1 minute read – Edit
Very nice post by Jessica Joy Kerr on the benefits and tradeoffs of event sourcing.
We can get a complete, consistent model of a small piece of the world using Event Sourcing. This is powerful but expensive.
Read more [blog.jessitron.com]
– Edit
Bernd Ruecker talks about how determine the right level of consistency in distributed applications.
– Edit
Evan You explains the principles behind the changes coming in Vue 3.0
– reinink.ca – Edit
Jonathan Reinink wrote another excellent blog post.
As much as possible, keep data fetching to the perimeter of your Laravel applications. What do I mean by this? In the simplest terms, it means running your database queries in your controllers.
Read more [reinink.ca]
In a very cool post, Rodrigo Pombo explains the internals of React by rewriting it's core from scratch.
We are going to rewrite React from scratch. Step by step. Following the architecture from the real React code but without all the optimizations and non-essential features.
Read more [pomb.us]
by Freek Van der Herten – 1 minute read – Edit
A couple of days ago my colleague Brent published a blogpost on Domain Oriented Laravel. In short, he makes the case for organising your code around business concepts or features. That might sound very "heavy" or daunting, but it's actually for easy to get started with.
In this short video I explain how you can use PhpStorm to refactor your code. Make up your own mind if you need this in your projects.
– twitter.com – Edit
Not adding an API until absolutely necessary lets us keep our model internal and lets us iterate as needed.
— Matthieu Napoli (@matthieunapoli) October 10, 2019
Read more [twitter.com]
Gergely Orosz argues that you should start with a simple design and try your best to keep it simple. I don't necessarily agree with everything in the post, but it's an interesting opinion nonetheless.
Software architecture best practices, enterprise architecture patterns, and formalized ways to describe systems are all tools that are useful to know of and might come in handy one day.
Read more [blog.pragmaticengineer.com]
– twitter.com – Edit
Extracting doesn’t guarantee simplicity. Sometimes extracting code into another module means I’ve smeared one “conceptual module” in my brain into two physical files. Now I can’t look at the whole thing at once, and their internal wiring is more prominent than it deserves. Oops.
— Dan Abramov (@dan_abramov) September 25, 2019
Read more [twitter.com]
An interesting opinion written by my colleague Seb.
Over the years I’ve experimented with different strategies to build user interfaces. From sprinkling JavaScript over server side templates to full-blown SPAs. My conclusion up until now: we can do better.
Read more [sebastiandedeyne.com]
– stefanbauer.me – Edit
I don't necessarly agree with every detail in this post, but it's very interesting to see how others structure larger projects.
In this article, I would like to show you an alternative way to organize your Laravel directory structure. I think the default structure is fine for the most projects. But when it comes down to larger projects I was looking for a different structure.
Read more [stefanbauer.me]
by Freek Van der Herten – 9 minute read – Edit
My buddy Mattias and I are running an uptime checker service called Oh Dear. Earlier this week, we've launched a new major feature: status pages.
In this blog post, I'd like to walk you through what status pages have to offer. We'll also dive deep in some technical details of the underlying Laravel app.