Its mainly about culture and convention. There should be a negotiation about what shape the data needs for front end and then the Business Analyst and data architecht should work out how to store it in the database and resurface it in the correct shape with an API in the middle layer. There are a whole host of other performance optimisations that can take place: Caching of shaped JSON objects to save expensive database calls, Paging requests to limit data set sizes, Graph QL . What I would say is that the front end should NOT be manipulating the shape of the data or running intersects between data sets; that is the responsibility of the middleware or data layer.
Secure database architechture is not a barrier to speedy delivery, it is however a protection against certain types of technical debt.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Its mainly about culture and convention. There should be a negotiation about what shape the data needs for front end and then the Business Analyst and data architecht should work out how to store it in the database and resurface it in the correct shape with an API in the middle layer. There are a whole host of other performance optimisations that can take place: Caching of shaped JSON objects to save expensive database calls, Paging requests to limit data set sizes, Graph QL . What I would say is that the front end should NOT be manipulating the shape of the data or running intersects between data sets; that is the responsibility of the middleware or data layer.
Secure database architechture is not a barrier to speedy delivery, it is however a protection against certain types of technical debt.