[FEATURE] Decomposition of key functionalities into libraries

Open
#59 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
go
Domain
api, backend

Research direction

Start by reviewing the initial work in the linked stackql/any-sdk repository and compare it with stackql's listed responsibilities: CRUD, authentication, transactions, and query analysis. The issue names no files, tests, entry points, or acceptance criteria, so the scope and definition of done need to be established before implementation.

Written by the indexing model from the issue text.

Description

enhancement v0.4

Feature Description

Operations performed by stackql are to be implemented through client agnostic libraries. This includes functionality such as:

  • CRUD functionality against resources:
    • openapi3 / http based.
    • External SQL data sources.
    • Calls against golang or C software libraries.
    • [Possible architecture] VM implementation for all of these, plus sync and recovery primitives.
  • Auth flows of various types.
  • Transaction support for composed CRUD operations.
  • Query analysis / validation.

Initial stages of this effort are in https://github.com/stackql/any-sdk

Strategy here is for useful functionality which is key to stackql to be available for other tooling in a language- and platform-agnostic manner.

Example(s)
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Possible Approaches or Libraries to Consider
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Dominant language
Go
Stars
0
Forks
0
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stackql/stackql-devel

All issues in stackql/stackql-devel

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.