Being a Java EE developer for a long time and trying to find a development platform in these times where more and more business logic is placed in the frontend code, Angular (NOT AngularJS) became a natural choice.
Being used to Java Server Faces with backend beans, coding with Angular is quite similar. You still have a HTML template and a separate class (Angular components) with the template logic, but now this is all part of the frontend code.
Also quite a bit of the code you would earlier place in EJB session beans can be put in Angular services, which can be injected into components using dependency injection.
All together with TypeScript which gives you static types, decorations (annotations), classes and interfaces that any Java developer will miss when coding with Javascript.
Now that the client / frontend does more and more of the traditional backend work, and the backend is more about providing data and access control than application business logic - Angular is a familiar platform for us used to Java EE.
Being used to Java Server Faces with backend beans, coding with Angular is quite similar. You still have a HTML template and a separate class (Angular components) with the template logic, but now this is all part of the frontend code.
Also quite a bit of the code you would earlier place in EJB session beans can be put in Angular services, which can be injected into components using dependency injection.
All together with TypeScript which gives you static types, decorations (annotations), classes and interfaces that any Java developer will miss when coding with Javascript.
Now that the client / frontend does more and more of the traditional backend work, and the backend is more about providing data and access control than application business logic - Angular is a familiar platform for us used to Java EE.
Comments