Sunday, 14 July 2019

Architecture decisions -- retrieving DB data from mysql

I am designing and building a program to manage and control some hardware configuration data, as well as generate configuration files for a COTS hardware suite. I've learned the basics of nodejs, express, react, and mysql, and have all the pieces working together.So, I'm hoping for some advice on how to architect the express model interface to the mysql server. This application is intended for use in an enterprise environment, with probably around 25-50 concurrent users, maybe up to a maximum of 200 in somewhat rare cases. When retrieving data from the database, should I be executing queries from the nodejs server, or should I be executing stored procedures? What is the generally recommended approaches? I've searched high-and-low for articles and posts about this, but haven't found anything compelling yet.I have some complex database stuff going on, including auditing almost every table for configuration control, so I have stored procedures and triggers set up to handle that. My thought is to use the stored procedures as an interface to the database. When I first started this project, a software engineer that I trust complained about the previous software saying, "all the stored procedures were in the database", so I guess I don't want to go down the same wrong path.​Any thoughts? Thanks in advance!

Submitted July 14, 2019 at 03:32PM by f6engineer

No comments:

Post a Comment