Can frontend and backend overcome their differences?
This is something that troubled me as well.
As someone who is primarily a backend programmer and as someone who loves structure in life, I was troubled by the fact that, with frontend, there often isn’t one best way to do something, but it’s more like – if it works, that’s that.
I found a solution to this while working on various projects, and I liked it a lot. This is Typescript. It is very interesting because it allows for object-oriented programming, which we are basically familiar with. It is very easy to use and it is compiled quickly. This looks like some kind of a consensus between frontend and backend, one that is to be strengthened even more in the future.
I was also delighted by the number of frameworks that have been developed in Typescript. Here I could mention NestJS, which I really liked and which I also have the opportunity to use on my current project.
Since what I am referring to is the Node world, I’d also say it has a perfectly developed ecosystem. We could even say that the number of libraries we can use is larger than with Java.
NestJS also makes it possible to connect microservices, whereby scaling is resolved very fast. Its performances per se are good, and adding new microservices – whether adding different microservices or scaling existing ones – is incredibly simple. And best of all it took me only a few hours to start using it.