I just watched the Spring AI Observability video, and I wanted to express my gratitude. The explanation was clear and concise, making the complex topic easy to understand. Thank you for sharing such valuable content!
Do you know when milestone is planned? There are bunch of spring-ai libs that are not available yet on this snapshot version - e.g. ollama, tika-document-reader
Great video as always.. :) But I have been wondering when watching your videos. You always use @Controller and @ResponseBody instead of @RestController, what is the benefit of one over the other?
Technically this is not a REST controller. It doesn't follow the REST rules. So it would be semantically wrong to annotate such controller with @RestController annotation. Although it would work and would be more concise.
I just watched the Spring AI Observability video, and I wanted to express my gratitude. The explanation was clear and concise, making the complex topic easy to understand. Thank you for sharing such valuable content!
Great info - enjoy the SpringOne conference.
Do you know when milestone is planned?
There are bunch of spring-ai libs that are not available yet on this snapshot version - e.g. ollama, tika-document-reader
So then, could you use that to calculate how much money you spent? Or is there a separate call to get that information?
Basically they intercept information that is provided in response to chat client as I recall.
But this is suitable of course
Who uses it? Who is it for? It seems just a toy, no production value.
Great video as always.. :) But I have been wondering when watching your videos. You always use @Controller and @ResponseBody instead of @RestController, what is the benefit of one over the other?
Technically this is not a REST controller. It doesn't follow the REST rules. So it would be semantically wrong to annotate such controller with @RestController annotation. Although it would work and would be more concise.