Tech Lead/Team Lead. Senior WebDev.
Intermediate Grade on Computer Systems-
High Grade on Web Application Development-
MBA (+Marketing+HHRR).
Studied a bit of law, economics and design
Location
Spain
Education
Higher Level Education Certificate on Web Application Development
well, even having those caveats (no static typing, single thread, performance...) still have some benefits such as being multi-platform (almost run everywhere), easy to learn and there are tools that "patches" JS "issues" such as TypeScript (javascript superset), and so, and browsers increased the performance of JS engines a lot too. It's used widely and consistently because there's no good supported option over the table to replace it yet.
Since you are a full-stack dev and use Laravel for API as well, which approach/tech do you use and recommend : REST or GraphQL ?
My current Laravel app is a stand alone, in which all requests are handled in web routes not api routes. However, chances are that I will have to build APIs for integration with other apps.
Tech Lead/Team Lead. Senior WebDev.
Intermediate Grade on Computer Systems-
High Grade on Web Application Development-
MBA (+Marketing+HHRR).
Studied a bit of law, economics and design
Location
Spain
Education
Higher Level Education Certificate on Web Application Development
There's no one to rule them all. You can use GraphQL with gRPC, or RESTful or... Depending on the needs of a project. My advice is to learn about and know the tech, then you can discern which stack is better for a job.
With GraphQL you can add a single endpoint for example but this could cause overheating on that endpoint. You can use services or microservices too with one or another.
Thanks for your advice.
One more question, for API authentication in Laravel : which tech/approach do you use/recommend : Passport, JWT, Sanctum or any other ? I am still considering which one I will use.
Tech Lead/Team Lead. Senior WebDev.
Intermediate Grade on Computer Systems-
High Grade on Web Application Development-
MBA (+Marketing+HHRR).
Studied a bit of law, economics and design
Location
Spain
Education
Higher Level Education Certificate on Web Application Development
well, even having those caveats (no static typing, single thread, performance...) still have some benefits such as being multi-platform (almost run everywhere), easy to learn and there are tools that "patches" JS "issues" such as TypeScript (javascript superset), and so, and browsers increased the performance of JS engines a lot too. It's used widely and consistently because there's no good supported option over the table to replace it yet.
Since you are a full-stack dev and use Laravel for API as well, which approach/tech do you use and recommend : REST or GraphQL ?
My current Laravel app is a stand alone, in which all requests are handled in web routes not api routes. However, chances are that I will have to build APIs for integration with other apps.
There's no one to rule them all. You can use GraphQL with gRPC, or RESTful or... Depending on the needs of a project. My advice is to learn about and know the tech, then you can discern which stack is better for a job.
With GraphQL you can add a single endpoint for example but this could cause overheating on that endpoint. You can use services or microservices too with one or another.
Thanks for your advice.
One more question, for API authentication in Laravel : which tech/approach do you use/recommend : Passport, JWT, Sanctum or any other ? I am still considering which one I will use.
Again check the differences and the compatibility or support on both front and back current stack, pick one and don't look back