asked on
Perl Script as a service
Hi all, looking for a little direction if you could point me the right way or offer some insight. Here's a little background info on the project.
I am developing a registration web portal for the parents in our district to register their students. the system is using IIS 7, MySQL, and Perl. We have a main Oracle based student database that the registration portal will pull data from using ODBC to keep a localized database of everything for registration so parents can manipulate it all they want without every changing anything on our main student database. When all is said and done, they will simply modify and data that needs to be changed, print out the PDF forms that we will serve up to them from the data they provided, and bring them into registration. Once we are satisfied with all the data, we can use it as an import back to our main database saving us loads of data entry time.
My question is this. Since they are two seperate systems, and if I have a new student who wants to register, I first must create that student in our main database so they exist, and either have an admin log into the registration web portal and offer the admin a method to import that student, or second option, have a constantly running script running in the background of the server without user intervention that will constantly do a query on both databases to see if there are any new students by comparing the lists between the two databases. If there is, then the script would have a subroutine to create the record, and the whole process would start all over again.
Is the later option a bad idea? I mean crap, I could always run it as a scheduled task to go off every 30 seconds. But I guess this may be bad form? Just because we CAN do something, doesn't mean we SHOULD, right?
I am developing a registration web portal for the parents in our district to register their students. the system is using IIS 7, MySQL, and Perl. We have a main Oracle based student database that the registration portal will pull data from using ODBC to keep a localized database of everything for registration so parents can manipulate it all they want without every changing anything on our main student database. When all is said and done, they will simply modify and data that needs to be changed, print out the PDF forms that we will serve up to them from the data they provided, and bring them into registration. Once we are satisfied with all the data, we can use it as an import back to our main database saving us loads of data entry time.
My question is this. Since they are two seperate systems, and if I have a new student who wants to register, I first must create that student in our main database so they exist, and either have an admin log into the registration web portal and offer the admin a method to import that student, or second option, have a constantly running script running in the background of the server without user intervention that will constantly do a query on both databases to see if there are any new students by comparing the lists between the two databases. If there is, then the script would have a subroutine to create the record, and the whole process would start all over again.
Is the later option a bad idea? I mean crap, I could always run it as a scheduled task to go off every 30 seconds. But I guess this may be bad form? Just because we CAN do something, doesn't mean we SHOULD, right?
Perl
Last Comment
FishMonger