Yes you can play with application.properties but application.yml has advantages on properties . Just try to find out the difference between these 2 you will understand

Hi @louellehamili1588, thank you for your question. Yes, you're correct. Database configurations can be declared in either `application.properties` or `application.yml` file, depending upon the developer's preference. The `.yml` (YAML) file is often known for its readability and ability to handle complex configurations, it's arguably much cleaner and less verbose compared to properties files. However, it's really up to the individual team/developer's preference. Both ways are acceptable. Please stay tuned for more videos on Java programming. Happy coding!

No buddy it should not be 404 , if with your valid input it's working and with invalid one it's not working how can we say this is 404 ?

Thank you for your insightful suggestions, @Kaushikraj9845! You're absolutely right, using Optional would indeed help in handling potential null values and enhancing the robustness of our application. I appreciate your keen eye for HTTP status codes too – a 'user not found' scenario should certainly return a 404 status.

As for your request on creating a Postman test suite, I think that's a fantastic idea! Exploring both positive and negative test scenarios would provide viewers with a comprehensive understanding of how the application behaves under different conditions. I'll be sure to keep that in mind for future videos.

Please continue to share your thoughts and ideas - it helps us create more valuable content for you and the entire Java Techie community. Thanks again for your feedback!

No we must need to throw the exception otherwise how it will identify the error Fallback method from the controller advice class

You're absolutely correct, @jeelanyelidandla2477. It's a common practice to extend exceptions from RuntimeException in Spring because it's an unchecked exception, allowing us to sidestep declaring it in our methods with 'throws'. This helps in maintaining cleaner code, which is often very important in a Spring environment. Great observation! Always remember, Java gives you the flexibility to handle exceptions in a way that best suits your specific application's needs. Thanks for your insightful comment! Keep exploring and happy coding.

404 always we need to use when resources are not available with the given url but here the url is reachable but the input field is not valid so either give 500 or bad request 400

Hi there @vaibhavsthakur, thank you for watching and sharing your insight. You have a valid point, it really makes sense. Generally, HTTP 404 is the status code for 'Not Found,' which would make more sense to use when a user isn't found. HTTP 500, on the other hand, is a 'Server Error.' In the video, we used HTTP 500 more as a catch-all for any errors that come up, but your comment highlights the importance of fine-tuning our status codes for accuracy in real-life scenarios. This feedback will benefit us all in our journey toward becoming better programmers. Thanks for sharing, keep tuning in for more Java concepts!

No udemy buddy but yes i offer live spring boot and microservice course in unacademy

Here is the link to know more about the course https://youtu.be/84KZa4dFLTo

Thank you for your interest, @johnvick8861! Currently, all of our content including tutorials and walkthroughs are available for free on our YouTube channel. I believe in making learning accessible to everyone, which is why all our tutorials reside here. If you want to support us, sharing our videos and subscribing to the channel helps a lot! Happy learning!