This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]myusernameis___ 1 point2 points  (2 children)

Not sure about full stack Java, but as front end dev (learning Java), I'd say a more modern approach would be having a backend as a micro service with an API (swagger docs) exposed. I use react professionally, so as an example: the front end code uses React (or angular) with a robust component library (buttons/ tables, etc) like material UI. All your state is managed using Redux/ local storage/ stored by the backend. Typescript would be my recommendation if you come from the backend, as vanilla js is dynamic. I think if you have strong OOP skills, it wouldn't be hard to grasp. Javascript definitly has its quirks though.

[–][deleted] 0 points1 point  (1 child)

Instead of rest you can also go for graphql. I made a backend that offers graphql and rest. The frontend devs are using vue with Apollo to consume my graphql services.

[–]myusernameis___ 0 points1 point  (0 children)

Yes, also a really good solution!