Yep, it's essentially the same thing. I guess EAV approach was the old way from before JSONField days. In both cases the cost of this flexibility and migration

Yep, it's essentially the same thing. I guess EAV approach was the old way from before JSONField days. In both cases the cost of this flexibility and migration-less data model extensibility is extra code paths and guards to check if these "optional" attributes are present or not. Spaghetti code anyone?