The #1 Spring Boot Starter you should include in every single application
HTML-код
- Опубликовано: 9 сен 2024
- In this tutorial we will discuss the #1 Spring Boot Starter you should start every application with.
🔗Resources & Links mentioned in this video:
👋🏻Connect with me:
Website: www.danvega.dev
Twitter: / therealdanvega
Github: github.com/dan...
LinkedIn: / danvega
Newsletter: www.danvega.de...
SUBSCRIBE TO MY CHANNEL: bit.ly/2re4GH0 ❤️
Brilliant!!! Not having looked at it in detail yet, I think the "beans" endpoint is going to be super-helpful.
Thanks for this.
Thank you, sir!
Hey Dan, your videos are very nice, keep up the good work!
Thank you for your sharing Dan
Sadly, I have an application in production currently with the Actuator functionality impaired due to a misconfiguration that only affected it. I found a related issue in Github. It happened by adding a custom jackson2Mapper bean without the jsr-310 configuration that /actuator/info depends on. The easiest way to resolve this case was to remove the custom bean and add a non_null property to tell boot about the extra config that we need when it creates the standard bean that actuator expects. Our next release is this weekend and the fix for this problem is included :)
Indeed a great starter.
Lovely!!! Super agradecido!
Great explanation🚀
One of the first dependencies I choose is Lombok. :-)
Devtools too
Very interesting episode :)
Extremly useful and interesting as usual. Thanks ❤
Very Nice, Excellent explanation
Great video! Please do a deep dive into the health endpoint.
I don't know much more about the health endpoint. What are you interested in hearing about?
@@DanVega Writing own and customizing health indicators. My service is up if service it depends on is up, but if the cache is down, it may not be that critical. Being able to tell the health of a data source when using multi-tenancy using AbstractRoutingDataSource.
Great introduction!!
Can you deal with security related to actuator in future videos?
Happy coding !!
is it normal that when i refresh my encoded properties it always get refreshed and shown in my return even if i didn't change them, for example my propertie is user.mdp=ENC(....) this always get returned in actuator refresh even if it didn't get changed
How are the endpoints used in prod? Do devs call them using something like Postman, do people make dashboards, or something else?
Likely a variety of ways? My apps currently deploy to TAS (Tanzu application service) where the endpoints are secured by the cloud foundry oauth token.
129th...Thanks Dan
Danny, buddy, old pal,
I've watched lots of your videos. You never include the Actuator.
Soucj for it being the Number One thing you include. 😂😂😂
*PAUSE THE VIDEO* I am guessing dev tools
I thought its spring-boot-starter-test