Several similar (but not the same) questions were asked 2 years ago, but were not 100% answered.
( Segmented Meteor App (s) - download only half of the client or two applications sharing a database ;
Meteor: different collections, different databases )
Since Meteor has changed quite a bit, it was interesting if there is a better way to do the following (I know about roles, publish a subscription, etc.):
A simple example: Let's say I have an application for ordering a restaurant with two portals:
(1) The consumer side, with the invoices, as well as the form for your food order and pay for it with a credit card (suppose that # is saved, not using Stripe, etc.).
(2) The administrator, with invoices, so that the restaurant can manage incoming orders and track payments, see credit card numbers.
Assuming greater complexity + very high security requirements, will it be structured as one monolithic meteorite application? Or there is a standard way to split it into 2 (for example, traditional MVC structures, you can have 3 DB DBs, 1 administrator DB, 1 DB for data with general confidentiality, such as credit card numbers - and 2 SPA clients). Interrupting it by 2 would be preferable for the following reasons:
(1) different types of accounts for 2 portals. Administrators require 2FA. I also prefer to have separate databases for security and backup protection.
(2) useful for code management / distribution purposes
(3), .