Wednesday, 17 May 2017

Backend application technology for an Angular front-end

I apologize if this question is too open ended. But I am struggling to get some of the principles to get started diving into this.

I am planning to build a fairly small demo app out of this seed (based on Angular 2): https://vmware.github.io/clarity/get-started

I'd like to render in an Angular UI some basic data that I keep in a back-end Redis database.

I am trying to find out what application layer I should be using to sit in between Redis and the Angular UI.

I am currently thinking of either using Ruby (just because I am slightly familiar with it) or Node.js.

Part of my struggling is because I am confused about the relation between Node.js and Angular 2 and I am wondering whether using Node code can help me integrating better and more easily with Angular (than with Ruby).

Other than using the same language/syntax (js), I have the gut feeling that I could more easily run a Node "app.js" file with some trivial business logic that reads from Redis and pass the result onto the Angular application. At least I could run the app.js logic on the same http instance where I am running the Angular application (my assumption).

If I wanted to use Ruby I have to use some web framework (e.g. Rails or Sinatra) to serve requests coming from the Angular application (e.g. in Angular I will have to make calls to http://myrubysrv/applogic).

Other than the language and this deployment detail, I am just wondering if passing variable from the application logic component into the Angular application is going to be easier if I use Node or the level of effort is going to be exactly the same whether I use Node or Ruby.

Thanks.



via mreferre

No comments:

Post a Comment