hey @ddoser020, I'll try to answer your questions.
-
I think that is very clear already for the dev? Backend and Frontend are already separated and thus should focus on their part, like Backend should handle Authentication, APIs, Security, Validation, and etc. While Frontend focuses on UI and UX, while frontend should also take into consideration how it calls API cause that would affect your performance too. honestly, this is a long discussion regarding this.
-
That depends on what is the requirement of your application, weight the pros and cons of it. Do you really need it to be SPA if all it does is just present information? What kind of data/information will it present? only you know that answer to that one. but to give you an answer you should go with Larave and Vue, practice your skill while developing simple applications. FYI I use
Laravel + VueNOTLaravel and Vue. There's a difference in both. The one you mentioned is Laravel and Vue though. -
It doesn't affect performance but it does affect how scalable, maintainable, flexible, reusable, and robust your code is, thus resulting in faster development time and it's easier to scale, maintain, reuse, and extend.
-
Just make sure your API is implemented properly to avoid security risks, it goes the same for your frontend too. Handle sensitive information properly in your frontend side. give only what your frontend really needs.
-
Don't be afraid of deployments, deploying your backend and frontend isn't that hard if you're using services. I'm assuming you would use a service or something. BUT handling everything like the server, installing the stack and configuring everything that is needed, and then deploying your application is a different story though. that's a whole lot of things to learn my friend. That's for a DevOp job already.
I prefer not to worry about that now and focus on developing your application, then just worry about it if you're really going to deploy it in the future.