The better design is not a hard delete, but a soft delete. So that means, the entry still remains in the DB but has a flag isActive = false, or isDeleted_ = true, and increment a version #. So the latest version of that entry will have either one of those flags to indicate it is 'deleted'.
I honestly like C# more overall as a language, but there is so many jobs in Java that I still code in it. C# is far less verbose and elegant, but Java has better ORM. I like C# more but Java is close.
DeleteMapping looks better and will accept actual DELETE requests. The way I did it works but only works with GET requests. Diffferent ways to achieve same outcome.
![Microservices using SpringBoot 3.0 | Full Example [NEW]](http://i.ytimg.com/vi/HFl2dzhVuUo/mqdefault.jpg)
![Spring MVC - 9. CRUD [Update]](http://i.ytimg.com/vi/J6n3orlP3yk/mqdefault.jpg)
The better design is not a hard delete, but a soft delete. So that means, the entry still remains in the DB but has a flag isActive = false, or isDeleted_ = true, and increment a version #. So the latest version of that entry will have either one of those flags to indicate it is 'deleted'.
HTML doesnt support Delete or Put Methods.
Hi Teddy
You made the Running App in Java and C#. Which did you enjoy more and why?
I honestly like C# more overall as a language, but there is so many jobs in Java that I still code in it. C# is far less verbose and elegant, but Java has better ORM. I like C# more but Java is close.
Like
What are the pros and cons of using @GetMapping over @DeleteMapping (besides the @Delete being a post request, and @Get a get request)?
DeleteMapping looks better and will accept actual DELETE requests. The way I did it works but only works with GET requests. Diffferent ways to achieve same outcome.
html forms unfortunately do not support DELETE and PUT requests