SPA or MPA, Laravel + Vue.js?

Question

Laravel

A large information system is being developed that supports many complex business processes and rules.
Users with different roles work, for which the content of the same page can be radically different.
It is necessary for each of the roles, depending on the current state of the document, to provide its own functionality, etc.
Questions related to SEO in this project do not matter.

Laravel + Vue.js will be used The

question is about choosing the architecture of the SPA / MPA application.

In SPAs, the primary concern is the security of the application. The need to make additional requests to check access to the document, actions, view modes, etc.
On the other hand, SPA looks preferable in terms of user friendliness.

I ask you to give advice in which direction to go and what you should especially pay attention to.

Answer 1

It's like with RISC architecture ...
If you can divide the system into partially independent processes - do MPA
If the complexity of processes reaches some abstract ceiling of understanding - break it down, those MPA
SPAs are when you want to show the same data from different angles.

Answer 2

SPA application is done separately. And it will be exchanged with Laravel or Lumen via api. All access control will be checked on the backend side. Middleware was not invented in vain. Yes, you can restrict access at the token level.

Answer 3

I made an application on Vue SPA (a portal with games, profiles, etc.), the problem arose as follows:
if there are dynamic scripts on the page, then to load them on the SPA, you need to build a big bike - load them into a frame, where they are lost Vue access. Especially if these scripts load some other scripts
, while with the standard MPA reload they are simply inserted into html