API & DB Info for Remote Glossary

[abhishek-goel]

Is there an API and DB schema available that will help me quickly spin up a DB, connect the API to it and have it running quickly? The goal is to reduce the amount of work to be done. Just like the documentation says to update config.json for Remote Glossary, if I can have application code that can be easily run with DB, things will be much faster.

You could have the application configured to use an in-memory DB by default.
Also, it would help if you provided a tool to quickly load the glossary.json to the DB or convert the json into a SQL file that I can run against the DB.

I know there can be a lot of options of application frameworks (e.g. SpringBoot, Quarkus, Micronaut, etc.) and DBs (e.g. PostGres, MongoDB, MySQL, etc.) but you could start off with an opinionated view and create something for the framework and DB you use internally at Capital One.

[amadib]

Hello @abhishek-goel - Appreciate your patience here! There is a sample glossary here and you can toggle the configuration here.

Hope this helps! Please let me know so I can close this issue 😄

[abhishek-goel]

@amadib
Unfortunately, this does not help. I know about the sample glossary already. I'd also discovered the enableRemoteLookup flag.

My point with this issue was to create a new feature request where an example of a DB & API is included for when someone wants to set enableRemoteLookup to true. It could be all AWS hosted set up using a Lambda and instructions for how to set up a basic DynamoDB or MongoDB. Just something more to help users of this awesome tool get setup more quickly without having to figure out too many things on their own.

You may choose to close this issue. But it would be great if you can show me how to raise a request for a new-feature/enhancement.