Metor + MongoDB + MSSQL - is it legal?

Question

SQL Server

The current project has been developed and is running on PHP + SQL Server, while the database exceeds a terabyte, the database itself also contains a lot of logic.
The service website contains a bunch of JavaScript noodles that receives data from the database via REST (in PHP). Everything was done 10 years ago. The growth of clients and the database is going on every month, there are still no caching of results and no queries to the database. I read the documentation on Angular and Meteor.
There was a desire to move to Meteor, but the base will have to be left, its use will be non-reactive.
That is, the site and all current information is kept in MongoDB, in fact it is a cache. On request, the cache warms up. The daemon also works, which once a minute (second) cleans the cache from old data, and also synchronizes all data with SQL Server.
Are there any best practices in my case, or am I going to use the wrong thing and Meteor is not for production at all?

Answer 1

https://github.com/numtel/meteor-mysql
In general, they promise native sql support out of the box info.meteor.com/blog/an-early-look-at-sql-in-meteor , it's better to wait until the guys from MDG do it it's in the core and don't use a third party package.
And yes, better use Angular or React because Blaze hasn't had any commits for a year https://github.com/meteor/blaze.
In general, think 100 times whether it makes sense to use a meteor without its "chips". Maybe it's better to remake Mean or Express?

Answer 2

I would advise you to move from your database to, for example, mysql
stackoverflow.com/questions/3917081/how-to-export-...
And if you need performance, then instead of meteor, angular and the like, use jquery + plugins.
And the cache can be written on the client side in local storage works with a bang.