quarkus-langchain4j-workshop
by quarkusio
This is a workshop to learn how to build AI-Infused applications with Quarkus and LangChain4j. It provides step-by-step instructions to guide you through the process.
Last updated: N/A
What is quarkus-langchain4j-workshop?
This workshop provides a hands-on experience to learn how to integrate Quarkus with LangChain4j to build AI-powered applications. It guides you through various steps to create a functional application.
How to use quarkus-langchain4j-workshop?
Follow the instructions available on the workshop website or serve them locally using the documentation in the docs/README.md file. Each step's final state is available in the step-XX directories. Navigate to the desired step directory and run ./mvnw quarkus:dev to start the application, which will be accessible at http://localhost:8080.
Key features of quarkus-langchain4j-workshop
Step-by-step instructions
Integration of Quarkus and LangChain4j
Practical examples
Final state of each step available
Local documentation serving
Use cases of quarkus-langchain4j-workshop
Building AI-powered chatbots
Creating intelligent document processing applications
Developing AI-driven recommendation systems
Implementing AI features in existing Quarkus applications
FAQ from quarkus-langchain4j-workshop
Where can I find the workshop instructions?
Where can I find the workshop instructions?
The instructions are available on the workshop website (https://quarkus.io/quarkus-workshop-langchain4j/) or locally in the docs/README.md file.
How do I run the application for a specific step?
How do I run the application for a specific step?
Navigate to the corresponding step-XX directory and run ./mvnw quarkus:dev.
Where does the application run?
Where does the application run?
The application runs on http://localhost:8080 by default.
What are the main technologies used in this workshop?
What are the main technologies used in this workshop?
The workshop focuses on Quarkus and LangChain4j.
Is there a final state for each step?
Is there a final state for each step?
Yes, the final state of each step is available in the step-XX directory.