Application and data architecture

24 posts
The Domain-Driven Design fallacy

The Domain-Driven Design fallacy

Most people get to know Domain-Driven Design through the tactical patterns. Concepts like Value Objects, Entities, Aggregates, Repositories and Event Sourcing are all strongly linked to DDD. That is most likely the reason why many people interpret Domain-Driven Design as a technical thing. This is quite a misconception though. When...

Kubernetes 101 - explaining the basics while running a Laravel application with Redis and MySQL.

Kubernetes 101 - explaining the basics while running a Laravel application with Redis and MySQL.

Kubernetes, also known as K8s, seems to be getting quite some attention these days in the container orchestration world. It even got some attention from Docker Inc. itself a while back, despite the fact that they have their own container management tool called Docker Swarm (and it’s as good...

A bird's eye view on API development

A bird's eye view on API development

So an API, that’s just output of some JSON code right? No problem, my framework does that automatically. Or if you just want an overview on some best practices, conventions and nifty ways people have done stuff before, this post has you covered. We won’t go in much...

Introduction to domain driven design

Introduction to domain driven design

As applications grow bigger and bigger, our codebase needs to accommodate for more and more business actions. After a while you will have code that impacts a large amount of business actions without knowing exactly what they are. Changes to that code become more and more stressful. We had long...

Thread carefully

Thread carefully

As far as I can remember, PHP has always had a terrible reputation at handling very heavy (or asynchronous) tasks. For a long while if you wanted to parallelize long tasks you had to resort to forking through pcntl_fork which had its own issues, and you couldn’t really...

Managing data flow on the client-side

Managing data flow on the client-side

I like to think of client-side applications as empty shells that get populated with data and where the source of that data can be anything: an object in your javascript code, an HTTP request, a JSON file, … Making sure this data flows correctly through your application is one hell of...

You’ve successfully subscribed to madewithlove
Welcome back! You’ve successfully signed in.
Great! You’ve successfully signed up.
Success! Your email is updated.
Your link has expired
Success! Check your email for magic link to sign-in.