In Spring Framework, Should I work with repository (Spring Data REST) result or create a RestController and service for each repository I want to work with? | Hashnode
In Spring Framework, Should I work with repository (Spring Data REST) result or create a RestController and service for each repository I want to work with?
I'd not recommended Spring Data REST approach for production level APIs as you wouldn't have much control on the REST resources you expose. Suppose in near future, you'd want to embed some data in each document of the result array before sending it as response then you'll end up following the second approach.
So, in a nutshell: Use Spring Data REST for quick prototypes where you want to CRUD of models whereas in production level APIs following separate Repository + Service + Rest Controller so that there will be consistent and clean code.
Vishwa Bhat
Technology Enthusiast
I'd not recommended Spring Data REST approach for production level APIs as you wouldn't have much control on the REST resources you expose. Suppose in near future, you'd want to embed some data in each document of the result array before sending it as response then you'll end up following the second approach.
So, in a nutshell: Use Spring Data REST for quick prototypes where you want to CRUD of models whereas in production level APIs following separate Repository + Service + Rest Controller so that there will be consistent and clean code.