Add Mongoid support to RubyLLM

XMLWordPrintableJSON

    • Type: Epic
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Integrations
    • None
    • RubyLLM
    • Ruby Drivers
    • None
    • Hide
      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?
      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • To Do
    • 0
    • 0
    • 0
    • 100
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Summary

      RubyLLM is the most popular solution for building AI powered applications on Rails - 3k Github stars.

      Currently, RubyLLM gem provides multiple features that works only when ActiveRecord is in place. We need to provide Mongoid support.

      Motivation

      Who is the affected end user?

      Ruby developers and teams using Mongoid with MongoDB who want to leverage RubyLLM for AI/LLM capabilities in their applications. Internal MongoDB advocates and partner engineers supporting these customers are also stakeholders.

      How does this affect the end user?

      At the moment Mongoid users cannot use the mainstream AI solution in their Rails apps. This makes Mongoid less attractive in the actual AI boom era.

      How likely is it that this problem or use case will occur?

      High likelihood. AI becomes an integral part of applications, so out customer will soon find out this limitation of Mongoid.

      If the problem does occur, what are the consequences and how severe are they?

      This can be a reason for developer to not choose Mongoid for their new app.

      Is this issue urgent?

      Moderate

      Is this ticket required by a downstream team?

      No

      Is this ticket only for tests?

      No

      Cast of Characters

      Engineering Lead:
      Document Author:
      POCers:
      Product Owner:
      Program Manager:
      Stakeholders:

      Channels & Docs

      Slack Channel

      [Scope Document|some.url]

      [Technical Design Document|some.url]

            Assignee:
            Unassigned
            Reporter:
            Dmitry Rybakov
            None
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              None
              None
              None
              None
              None
              None