Build Web application on two separated frameworks - laravel

My team has to develop a project for a large fleet company which will be fleet management system. we will use Laravel framework to build it. My question is "Does it considered a good practice to build the Backend on Laravel by implementing APIs only then to have another framework like Vue.js to Build the Frontend?

Related

Strapi as general backend framework to build social app?

I understand Strapi is a headless CMS. But I wonder if it can be used as a general backend framework (like Django) to build a social app.
By looking at its CRUD API capabilities, I feel it is possible; but on the other hand, the way Strapi boasts its user management and RBAC makes me feel it is very much tailored for internally managed users
Can someone share your understanding and experience toward Strapi?

What exactly is a Full-stack development in Spring Boot with Java?

I was under the impression that Angular is integrated as a front-end in the same project as Spring to avail beautiful looking websites as I did once in a previous project in a company.
But as I started looking some videos on youtube and udemy, they are creating a separate project for both angular and spring running on different ports 4200 and 8080.
Is this what a full-stack development is and is this what the companies are asking for in the interviews nowadays? Sorry if the question seems from 2015.
You are correct, each of them is an ecosystem that communicates with each other via nowadays mostly rest.
Each of the code is compiled separately also, typescript and java.
As for full-stack requirements for job its most of the time on one side you have for an example spring boot microservice that does some logic and exposes those results on specific URLs, and you consume those results with your frontend and display them accordingly.
Now, when it comes to frontend you can simply mock values and do your development instead of waiting for someone to finish their backend and after they are done you just write it to the specification that they provide. Most of the time its used Open API ( ex Swagger ).
But basically if you call yourself fullstack developer you need to be able to write backend that emits responses with some results, and write frontend that consumes those responses and displays them. Front side of an application as well as back side.
There are approaches where you use only JS ( nodejs for backend, react or angular for frontend and mongodb for database ), but if you end up in some company where are old-school people, it will be Java on backend and they are looking for youngsters that are Jedi Knights in JS, at least that is what my company did a month ago.

Creating Microservices in ATG 10.2

As part of requirements, there is an expectation to create microservices for an existing ecommerce platform. The current architecture runs on ATG 10.2 version and has some rest API's hosted on it.
Given the fact that ATG is a monolithic ecommerce framework, is there any way that we can create microservices in ATG? Even if we are able to do so, how will they run as independent services? i mean how can we deploy them and test them in other environment? Wanted to know the technical feasibility of creating microservices on ATG ecommerce platform.
Perhaps you need to define how your microservices are supposed to work first. If you were to, for example, expose the ATG Profile as a microservice, it won't, by itself, run in another environment, it simply means that you can expose the functionality for consumption by a different system via the service. Alternatively you can expose a Profile module on a different system and try to consume it within ATG. That too is possible.
In a nutshell you can integrate various open source libraries into your ATG stack to build and expose the functionality of the monolithic application into microservices. To get started, read up about webmvc, oxm, hateoas, plugin-core, springtonucleus and perhaps dozer.
Perhaps you need to define your architecture first before asking a much more specific question here. The real answer is just too long.

advantages of webapi in comparison with web services and wcf

i was asked in an interview the following question about webapi
Why we need webapi?
I told "the services that are created in webapi can be used across wide range of devices like laptop, desktop, tablet and mobiles."
Then the interviewer asked why it cannot be done using web services and wcf?
I don't know the answer.
Can anyone let me know the answer.
Copying the title of your question into a search engine yielded the following link.
WCF and ASP.NET Web API
WCF is Microsoft’s unified programming model for building
service-oriented applications. It enables developers to build secure,
reliable, transacted solutions that integrate across platforms and
interoperate with existing investments. (ASP.NET Web API) is a framework
that makes it easy to build HTTP services that reach a broad range of
clients, including browsers and mobile devices. ASP.NET Web API is an
ideal platform for building RESTful applications on the .NET
Framework.
There is also a table detailing when you should use which.

Can I get the projects links via the SonarQube Web Service API

We want to get the project links (Home, Continuous integration,...) via the SonarQube Web Service API.
The links belong to the CoreProperties - https://github.com/SonarSource/sonarqube/blob/master/sonar-plugin-api/src/main/java/org/sonar/api/CoreProperties.java
Is it possible to read them via the API?
This is not possible yet. But with the UI refactoring that is currently done on 5.2, this is likely that such a WS will be developed.

Resources