Symfony

I've had good experiences moving from Supervisord to using systemd for managing processes, especially for setups involving RabbitMQ and Symfony. Systemd not only integrates well with the system, offering better control and management, but it also simplifies logging through journalctl and handles automatic restarts seamlessly.

Here's what I did to make the switch: - Craft a Service File: I wrote a .service file in /etc/systemd/system/ to describe my service. It includes details on how to start and stop the process, among other things. - Set Up Service Behavior: Inside this file, I specified commands like ExecStart for launching my process, Restart to ensure it always restarts after failure, and set the User to define which user runs the process. - Enable and Launch the Service: With systemctl enable my-service.service, I made sure my service would start on boot, and systemctl start my-service.service got it running right away. - Manage and Log: Whenever I needed to check on things, journalctl was there for logs, and systemctl helped me manage the service (like checking its status or restarting it). - Switching to systemd resolved the disconnection issues I faced without needing any workarounds like restartingI've had good experiences moving from Supervisord to using systemd for managing processes, especially for setups involving RabbitMQ and Symfony. Systemd not only integrates well with the system, offering better control and management, but it also simplifies logging through journalctl and handles automatic restarts seamlessly.

Here's what I did to make the switch: - Craft a Service File: I wrote a .service file in /etc/systemd/system/ to describe my service. It includes details on how to start and stop the process, among other things. - Set Up Service Behavior: Inside this file, I specified commands like ExecStart for launching my process, Restart to ensure it always restarts after failure, and set the User to define which user runs the process. - Enable and Launch the Service: With systemctl enable my-service.service, I made sure my service would start on boot, and systemctl start my-service.service got it running right away. - Manage and Log: Whenever I needed to check on things, journalctl was there for logs, and systemctl helped me manage the service (like checking its status or restarting it). - Switching to systemd resolved the disconnection issues I faced without needing any workarounds like restart jobs. It felt like a cleaner, more reliable approach.

Hi. I guess it all depends on what your goal is. If you wanna make fast prototyping Django or ExpressJNodeJS might be really good candidates. You can write your services quickly and easily by using anyone of them. Maybe we can also put Laravel in the same category.

Symfony is also another application framework that comes with many reusable components. It provides great flexibility with the configuration and dependency management solutions. So that you can inject or override anything, anytime without doing something hack-ish. You don't have to depend on any components that come with the framework and, replace them with whatever you prefer unless encounter any integration issues. I can say that Laravel also provides most of the Symfony futures as it uses its components under the hood. However, my personal experience with Laravel was not so good because it made me feel like I use a modernized version of Codeigniter. But anyway. :) So if I have to choose one of them, I would choose Symfony.

From the backend perspective, all of those have some pros and cons. For example, If strict type declaration is important for you and you don't like code magics like monkey patching etc., maybe Python and NodeJS might not be good candidates and maybe you could choose Symfony/php. However, in this case, you'll be missed out on the most powerful future of NodeJS which is non-blocking io. if you plan to do IO-intensive works, I think it would be a big loss.

So, maybe I can recommend you to have a look at typescript + NestJS also. https://nestjs.com/ The futures that NestJS provides might be a good balance between the strengths of Symfony and NodeJS.

As I'm backend dev., I haven't work too many frontend projects but from my personal experience, I loved ReactJS more than Vue although Vue was simpler. Maybe a front-end developer can give us more helpful details about those.

Hope it helps.

you can create new controllers straight to your services, in the end you will server as an api

1 - make sure that you do not have dependencies coupled on your controller and everything as well implemented on their respective services layer.

2 - just make a v2 still comunicate with your services, but in your v2 you should return json whitin your new controller, don't forget to specify a new path for those services that will be use your service as api prefix: /api

You need PIM and Drupal can both do eCommerce site and PIM catalog with many modules. Tests are available and extension are coded as Open Source too. Smaller cost of ownership. Require knowledge and more debug to get good result. From version 10 it will provide automatic updates that required for e-commerce in term of security

hey it is my first comment on stackshare :-) let me say, i am developer for/with prestashop and shopware

both using symfony but in different versions both system can completly customized in templates, modules, hooks/actions ....

i think it depends on the amount of products, countries and taxes too

I too have a background in PHP, but found Svelte super easy to pick up. In many ways I found it similar to working in php with a template engine like Handlebars (it has syntax that is very similar to Handlebars). If you have experience with Laravel, you could also look at Vue.js, which works great with Laravel and might give you the best of both-worlds.

I'd say that Nuxt looks more stable/mature, the team is growing, and the dev experience is 👌. It's THE framework I recommend to most Prismic users. Super easy to understand and maintain, and their doc is getting better and better. They have good integrations with CMSs if you ever need one, with very well maintained plugins (modules in Nuxt) by the core team and by the community. So also a huge ecosystem around it! From the Prismic side, I see its usage growing super fast, so I guess I'm not the only person loving Nuxt :) See: https://www.npmjs.com/package/@nuxtjs/prismic

Go with Node.js. There's something really satisfying about being able to use a single language across your entire tech stack. Especially once you integrate GraphQL, which is effectively JSON.

Your second best option is Go, but the ecosystem around Node.js is quite a bit stronger. This will play a big factor when you start building functionality like file management, messaging (especially in real-time), and authentication. The libraries and documentation are just stronger for Node.