* Warehouse Management System - Barcode scanner, mobile app (Ionic), dashboard app.
* Vodafone Site Management - App for managing over 100 types of devices (with dynamically generated forms for each type), geolocation tools, 3D room editor (three.js), charts, and real-time data synchronization across tabs.
* SAP/Spartacus plugin for the Sony e-shops.
* correkt.com - e-commerce site with modern UI, SSR, zoneless architecture, Tailwind CSS 4, hydration, and various performance, SEO, and Core Web Vitals optimizations;
* surex.com (frontend) - insurance survey app with multiple complicated forms, rewritten from AngularJS to modern Angular.
* and 30+ other projects, from small startups and individuals to large enterprise companies.
I guess the point is that you're already doing it for postgres. You alrrady need persistent storage for your app, and the same engine can handle your queuing needs.
Exactly, if you’re already doing it for Postgres and Postgres can do the job well enough to meet your requirements, you’re only adding more cost and complexity by deploying Redis too.
Not sure. As software becomes a commodity I can see the "old school" like tech slowing down (e.g. programming languages, frameworks frontend and backend, etc). The need for a better programming language is less now since LLM's are the ones writing code anyway more so these days - the pain isn't felt necessarily by the writer of the code to be more concise/expressive. The ones that do come out will probably have more specific communities for them (e.g. AI)
reply