quarkus-langchain4j-workshop

Created By
quarkusioa year ago
Quarkus Langchain4J Workshop
Overview

What is Quarkus Langchain4J Workshop?

The Quarkus Langchain4J Workshop is an educational program designed to teach developers how to build AI-infused applications using the Quarkus framework and LangChain4j library.

How to use Quarkus Langchain4J Workshop?

To participate in the workshop, follow the step-by-step instructions available on the workshop website. You can also serve the instructions locally by following the docs/README file. Each step's final state can be accessed in the corresponding step-XX directory, and you can run the application using the command:

./mvnw quarkus:dev

The application will be accessible at http://localhost:8080.

Key features of Quarkus Langchain4J Workshop?

  • Comprehensive step-by-step guidance for building AI applications.
  • Integration with Quarkus and LangChain4j for enhanced AI capabilities.
  • Local development setup for hands-on learning.

Use cases of Quarkus Langchain4J Workshop?

  1. Building chatbots that leverage AI for natural language processing.
  2. Developing AI-infused applications that require real-time data processing.
  3. Learning best practices for using Quarkus in AI projects.

FAQ from Quarkus Langchain4J Workshop?

  • Is prior knowledge of Quarkus required?

While prior knowledge is beneficial, the workshop is designed for all skill levels, including beginners.

  • Can I contribute to the workshop?

Yes! Contributions are welcome, and you can find guidelines in the repository.

  • Is the workshop free to access?

Yes! The workshop materials are freely available for everyone.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
quarkusio
Star
40
Language
Java
License
Apache-2.0 license

Recommend Servers

View All
Alloy

2 days ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

8 hours ago
Crevio

a day ago