Hi Milad, Angular 2 is well suited here. But before you start on the front end, you need to make a couple of decisions. You need to communicate between "parts". What is it that you need to communicate? How important is this communication? Does it need to be real-time? All of it, or just some hot parts? Design your back-end to accommodate for this first. Choose how you want to communicate (websockets/ssp/ajax/...). Probably a mix. Read into microservices. bottom-line communication and storage are back-end tasks in systems like this. Design this API well, and your frontend will become much more robust, and easier to maintain.
Regards Sander -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
