GraphQl and NextJS 13+ for multiple, concurrent/parallel DB queries?
I know this could be a problem with architecture/design, but how would you most efficiently query (read-only) 15-20 MySQL DBs at the same time?
There's a legacy internal tool at work they apparently want me to remake and they explained this is what they're doing with the current version. It can take very long to perform queries related to a single user search, which will usually query 15-20 databases that are on-prem. The internal tool is also hosted with on-prem infrastructure via perl, CGI and an nginx or Apache server (very old, I know....). Only about 30 people will be using this tool. The app itself will only perform read queries, and tracks the history, status and details of their web service API calls throughout all their environments (5 environments with 3-4 DB for each). They suggested graphQL for the queries but I'm not sure if that would actually make it faster. Any ideas?
The architect on my team said to use NextJS or dotnet, whatever I'm more comfortable with for the UI, and gave no acceptance criteria or any sort of official writeup/ticket. Not sure if this is just due to them being busy but they said "we want to see how well you work like this". I'm not sure if these tools would actually solve the problem.
There's a legacy internal tool at work they apparently want me to remake and they explained this is what they're doing with the current version. It can take very long to perform queries related to a single user search, which will usually query 15-20 databases that are on-prem. The internal tool is also hosted with on-prem infrastructure via perl, CGI and an nginx or Apache server (very old, I know....). Only about 30 people will be using this tool. The app itself will only perform read queries, and tracks the history, status and details of their web service API calls throughout all their environments (5 environments with 3-4 DB for each). They suggested graphQL for the queries but I'm not sure if that would actually make it faster. Any ideas?
The architect on my team said to use NextJS or dotnet, whatever I'm more comfortable with for the UI, and gave no acceptance criteria or any sort of official writeup/ticket. Not sure if this is just due to them being busy but they said "we want to see how well you work like this". I'm not sure if these tools would actually solve the problem.
