What is the best folder structure in a microservice architecture project using serverless framework? [on hold] - node.js

Please suggest me the proper project structure in microservices pattern serverless.


Angular Nativescript mono repo with non-Nativescript projects

I am working in a team that is using a monolithic repository for web-based Angular projects. This is using the Angular CLI projects (libs/applications) setup.
For one of our web projects, we want to add NativeScript mobile applications. The intention is reusing a few of our libs (model/validation logic) for the mobile applications.
Is it possible to 'ng generate Nativescript Application etc', so that it exists within our current monolithic project structure?
Any help on this would be appreciated!

Microservices in Nodejs?

I'm trying to develop a microservice in Node.js. I wish to develop a microservice for authentication using jsonwebtokens. I'm trying to make it using SenecaJS. Shall I use any other framework/tool? What should be my approach? Unable to find proper documentations. What seneca plugins can I use?
I use seneca-jwt. Very good plugin.

JHipster vs MEAN-Stack vs MERN-Stack

I am familiar with developing AngularJS and Angular 2/4 UIs utilizing JHipster 4's JPA CRUD scaffolding but it feels unnatural. And I think developing MEAN-Stack UIs is the path of highest productivity.
How much refactoring is involved utilizing MEAN-Stack UIs with JHipster JPA (MongoDB) and Angular scaffolding?
Also, if using JHipster's new React support, how much refactoring is required to utilize MERN-Stack UIs with JHipster JPA (MongoDB) and React scaffolding?
Oh, I forget to mention my development target is PWAs (Progressive Web Apps) aka mobile first design.
You'll have to fork the jHipster generator, add your own templates for mongodb, express.js and nodejs.
The server side templates are mostly in generators/entity-server/templates, and generators/server/templates. These template files are written as EJS templates (EJS).
One of the steps during the app generation is to create JSON files from the JDL file. You can run just the json creation using a command like this:
yo jhipster:import-jdl jhipster-jdl.jh --db=mysql --json-only=true
The JSON files will get created in .jhipster folder (note the "." in front which makes the folder hidden) under your project.
Create your own sub-generators similar to the "server" and "entity-server" sub-generators, that use the generated JSON. The templates will have JavaScript that uses nodejs, express.js and mongodb, instead of Java with JPA, and Spring Boot.
This is not going to be easy, although you could follow the JHipster code and create the sub-generators.
I guess someone might have already done all this in one of the forks from JHipster, in which case you might want to start from there.

How to design project solution for webapi2 with angularjs project?

I am starting new project with angularjs with webapi. This project will be e-commerce site. There is iOS and Android app also. We are going to develop APIs so that Android and iOS team can consume our APIs. Also we are going to consume APIs using angularjs for web application. I need some inputs before starting project. I am planning to design separate solutions for APIs and my web application. I am using visual studio for development environment for front end. I am confused about which template should I use in vs2015 to develop front end? My front-end will contains angular js files,HTML pages and CSS files. Second point is there is a Arabic version of this website so I am storing all Arabic words in resource file. Where should I store my resource files? In API project or front end project? May I get some inputs to develop solution architecture? Also what is the standard way of angularjs project folder structure? Any help would be appreciated. Thank you.

How to set up Angular JS Maven project for UI and Spring Rest Maven project on server side?

I am newbie to Angular JS and also Spring REST API's. I am planning to develop 2 seperate applications, where 1st Project is UI which will be developed with Angular JS and 2nd project is Server side where it exposes REST calls to aforesaid UI project, for that I am planning to go for Spring REST framework. Both the projects will be using Maven build tool. Wanted to some inputs and tutorial links which really help me.
I'd go with an application generator that will set you up with an angularjs front end and a spring-boot backend. check out jhipster: http://jhipster.github.io/
I would recommend to build the fronted (UI) with gulp.js and manage dependencies with npm. To call node/npm/gulp from Maven I recommend the Frontend Maven Plugin. You can have a look at Sagan (the codebase for the spring.io website) - they are doing the same (with Gradle instead of Maven).
I have had same kind of case in one of my projects. The idea of this setup is that you have frontend and backend separated so that they would be easier to manage. You would transfer data from frontend to backend via REST web service.
Here's what you can do:
Setup three maven projects, where one is working as parent and two others as child projects. One of child projects is for backend (Java, Hibernate, Database connections, Spring and so on...). Other child project is for frontend.
Frontend project can be generated with Yeoman. This is nice tool where you can generate project structures. For example you can tell Yeoman to generate MEAN project and it will build MEAN project with required frameworks. There are many templates you can generate your project based on. Make sure that your project contains Grunt framework because there you can configure it to listen your backend project.
Once you have all your projects setup, then configure your Grunt file. You need to setup a proxy that listens your backend side (usually http://localhost:port). You need to make sure what's your backend server port.
With these steps you can now easily build your project and install whatever frameworks for frontend and backend. It will also be easy to manage, since you have moduled those projects.
Remember to deploy your backend maven to your server. Otherwise this setup won't work.