yes we can do similar kind of thing in Frontend also we were doing in our project where we have centralized service that will laoad the manifest based on a particuar client and eeach client will have a differnt view of the page
Thank you. I have a question. What if for a new feature an entity needs a database migration, for instance, a new column with required value (NOT NULL) must be added? How would you save the entity if the flag is set to false for this feature?
We always need to plan for a backwards compatible option. So the column cannot be not null in the initial stage. Later when the feature is live, backfilling has to be done for old rows and then the column should be made not null
Awesome video💯🙌. In trunk based development why would a feature will be merged in main branch if it is not yet ready to be used?. Is it to avoid major merge conflicts
We generally use static (property based ) and customer specific (db level). I'm just wondering 🤔 about config server, the major disadvantage is the rest call.
Instead of rest call (pull) you can use SSE or websocket (push) and get the changes in real time, save them in memory, but on the other side it is getting much more complex.
