DEV Community

Discussion on: DO NOT trust your frontend validators

 
latobibor profile image
András Tóth

The point is, you are better off if you think about the bottlenecks than if you are not.

As a side note it horrifies me whenever I read "80-90% backend applications are simple CRUD applications, therefore they can be autogenerated from a document.". If your application is a simple CRUD you either don't have data consistency or an actual useful, sellable product.

Thread Thread
 
polterguy profile image
Thomas Hansen • Edited

If your application is a simple CRUD you either don't have data consistency or an actual useful, sellable product

Define CRUD. Our "CRUD" generator allows you to apply.

  • reCAPTCHA values for individual verbs towards individual tables
  • Authorisation requirements for individual verbs towards individual tables
  • Row level security implying for instance users cannot see individual records that aren't their own "property"
  • Decide which rows are included in which CRUD verb endpoint
  • Automagically takes care of foreign keys, adding auto complete widgets in the frontend when you've got a foreign key, doing lookups into the referenced table
  • Publishing socket messages upon write invocations towards data
  • Implement caching
  • Log invocations
  • Add validators server side for individual fields
  • Etc, etc, etc ...

I'd say that covers about 80% to 90% of the stuff me and you typically do, assuming your background is enterprise software development ... ;)

... unless of course you're one of these guys always looking for an opportunity to make stuff more complex ... :/

an actual useful, sellable product

Psst, Microsoft Office Access ...?

Last time I checked it was selling pretty decent ...? ;)