Advanced Laravel: Avoid unified data models to make software development easier

Shawn McCool (08.Jun.2018 at 13:30, 45 min)
Talk at Dutch PHP Conference 2018 (English - US)

Rating: 4 of 5

The traditional approach to data modeling is to create a single unified model. We use one User model to represent users in each and every feature. As this relationship graph grows, the data model becomes increasingly difficult to change.

In this session we’ll explore ways to create useful Eloquent data models that are smaller, more focused, and are much easier to change.

This session is for beginning or expert developers of applications large or small.

Who are you?

Claim talk

Talk claims have been moved to the new Joind.in site.

Please login to the new site to claim your talk

Want to comment on this talk? Log in or create a new account or comment anonymously

Write a comment

 
Please note: you are not logged in and will be posting anonymously!
= eight minus two

Comments

Rating: 2 of 5

08.Jun.2018 at 14:18 by Agustin Villalba (23 comments) via Web2 LIVE

Sometimes it promoted bad practices

Rating: 4 of 5

08.Jun.2018 at 15:45 by Rico Humme (4 comments) via Joind.in iPhone app

Interesting thoughts on approach of decoupling your models. Never thought of models over barriers through events.

Rating: 5 of 5

08.Jun.2018 at 18:17 by Jeroen v.d. Gulik (98 comments) via Joind.in iPhone app

Honestly one of the most approachable talks when it comes to boundaries

Rating: 3 of 5

08.Jun.2018 at 20:30 by Jochem Fuchs (58 comments) via Web2 LIVE

Not a bad talk. I've seen much better talks from Shawn, but it was nevertheless a very useful talk with good points

Rating: 3 of 5

09.Jun.2018 at 10:22 by Onno Lissenberg (58 comments) via Web2 LIVE

Nice talk.

Rating: 2 of 5

09.Jun.2018 at 23:38 by A R S (12 comments) via Web2 LIVE

Interesting take on making models more loosely coupled, but comes with a important down sides that the speaker didn't mention or glossed over. This kind of coupling breaks the 'one source of truth' rule, misconfigured events or outside changes could create invalid data. There is very little preventing (for example) speaker.name and talk.speakerName having different values.

Rating: 5 of 5

10.Jun.2018 at 03:21 by Tim Huijzers (25 comments) via Web2 LIVE

Very interesting approach on how to explain boundaries.

Rating: 5 of 5

10.Jun.2018 at 17:23 by Srdjan Vranac (122 comments) via Web2 LIVE

The idea this talk conveys is really important, I had some analysis paralysis regarding the possible approaches to this matter, and this cleared it up nicely.

Rating: 5 of 5

11.Jun.2018 at 09:48 by Robert Basic (97 comments) via Web2 LIVE

I felt that this talk is less about "this is how you should do things", but more of a talk to challenge the status quo and lets try something new and different to make things better because the speaker is not happy with how things are in the web dev community. Not a lot of people are out there trying to push the boundaries, but Shawn is one of them.

Rating: 3 of 5

11.Jun.2018 at 13:27 by Onno Marsman (78 comments) via Web2 LIVE

Great insight in how to prevent a model from exploding for different feature. I think it wouldn't be wise to store everything redundant, but there could be use cases where this might be useful.

Rating: 4 of 5

11.Jun.2018 at 18:28 by Ronald D. (42 comments) via Web2 LIVE

Good talk, useful insights into boundaries.

Rating: 4 of 5

14.Jun.2018 at 19:03 by Arnout Boks (70 comments) via Web2 LIVE

Nice talk, but would have preferred some more content about the tradeoffs involved in your approach, also with regards to testability. Also, I think the message you're trying to get across is easily understood: instead of a gentle introduction to bounded contexts people might have interpreted it as an advice to create a separate datamodel for every (small) feature. That might be something to watch out for.

© Joind.in 2018