Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

API Wrapper For FMTM Splitter Microservice #63

Open
spwoodcock opened this issue Oct 28, 2024 · 0 comments
Open

API Wrapper For FMTM Splitter Microservice #63

spwoodcock opened this issue Oct 28, 2024 · 0 comments
Labels
effort:medium Likely a day or two priority:low Backlog of tasks that will be addressed in time

Comments

@spwoodcock
Copy link
Member

Is your feature request related to a problem? Please describe.

  • Follow on from Modularisation of FMTM Splitter #62
  • Once modularlised, we should consider an approach of having this as a microservice, with a very light http wrapper.
  • Having a Python module is all well and good, but this relies on a database: ideally the user has a option to deploy with an existing db or a bundled db with the microservice.
  • If a user could simply deploy this with a few commands, then pass in geojson files for splitting, it would be a much more user friendly tool and could potentially be adopted by others.

Describe the solution you'd like

Many options:

  • Small FastAPI service to wrap the Python module here. Note we need to maintain /update this though...
  • Something more lightweight possibly? We simply need a HTTP request to send a JSON payload, trigger SQL, return a JSON payload.

Additional context

  • We can probably keep this as a Python package published on pypi too.
  • That will allow flexibility for how the user decides to deploy (bundled in their own app, or standalone microservice).
@spwoodcock spwoodcock added priority:low Backlog of tasks that will be addressed in time effort:medium Likely a day or two labels Oct 29, 2024
@spwoodcock spwoodcock added this to the Modularlisation milestone Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort:medium Likely a day or two priority:low Backlog of tasks that will be addressed in time
Projects
None yet
Development

No branches or pull requests

1 participant