When you use non-atomic attributes in a relation, you loose portability of the model, indeses, and constraints. JSON columns for anything else than cache is a bad idea.
@carre_sam@Pat_Stan_@ecrmnn You also loose portability, indexes, and constraints. Non-atomic attributes of relations are an anti-pattern. Unless it’s a cache of something that’s available elsewhere, don’t use it
@ecrmnn Sooner or later, this kind of things will bite you. Take it from me, a dev that saw the birth of all the PHP frameworks, you should observe the normal forms and create the necessary structures.
When researching strategies, seek patterns over stories. One person succeeding means nothing. 100 people succeeding is a signal.
When explaining strategies, emphasize stories over patterns. People forget numbers and charts. Everyone remembers a great story.
–@JamesClear
@AshAllenDesign Excellent 👌 you could perhaps add a note: transactions hinders scaling 😣 because they need to happen in one place. Could be the topic of next article?
@ModernizingPHP When the code is ad-hoc, it's virtually impossible to test. Problems like this often arise when management decides scope, deadlines, and resources. Happens a lot in small companies grinding for the next penny...
@J_Lieu@Sarthaksavvy At that scale, I wouldn't. At that scale, Laravel would probably be one of the many, many different technologies the company's running. And architecture performance design would become paramount.