Povilas Brilius

I think that you should rely on micro-parts engineering and implement that frontend stuff from scratch likewise employing webpack.js. It's an easy approach to pump with the latter meaning that you will have no problem with the stuff like fussing or hustling around.

There's no problem with ImageMagick installation on the server, though have in mind, that it's a full-stack development, you cannot be hacking the website and its app configuring some weird extensions that requires backend intervention and not having access to it.

It's a general development question, be more specific, because /dev/std... is a generic approach, not a targeted development. You want to develop PHP or Java? Both are good in their terms, but it's your decision. For PHP Laravel is a robust and exhaustive console enabled framework, featuring rich integrations with virtualization & REST. On the other hand, Spring will bring you learning curve if you are switching from PHP and so on. Try to match your needs with project requirements, it will be easier.

As far as I know, MySQL Workbench doesn't handle Microsoft connections, including Azure, you should try Microsoft solutions such as MS VS Code.

Laravel is pretty good at working with databases and APIs especially, invoke artisan presenter generate CLI command and you are done with an entity. So, to continue, just exemplify this instance to the benefits of the receiver, i. e. your database and you are way ahead of competitors. Not sure about express.js, but backend is necessary to this database, as in general persistence driven application.

Laravel in this instance, because for unexperienced freshcomers it's rather easy to integrate, it has already embedded @Eloquent #ORM, models are quite normally comprised from scratch, no need to import from database layer and adjust them later, so it's in general an easy and comprehensive tool to install, use & exploit to the furthest.

@Kibana, of course, because @Grafana looks like amateur sort of solution, crammed with query builder grouping aggregates, but in essence, as recommended by CERN - KIbana is the corporate (startup vectored) decision.

Furthermore, @Kibana comes with complexity adhering ELK stack, whereas @InfluxDB + @Grafana & co. recently have become sophisticated development conglomerate instead of advancing towards a understandable installation step by step inheritance.