Daily Shaarli
February 12, 2026
- A simple queue.json
- Batching with group commit
- Use a brokered group commit to eliminate contention over the queue object
- HA brokered group commit to handle unfinished job or broker machine die
Similarly to the job system we built at work, it guarantees at-least-once delivery.
I don't know if the pattern becomes too complex to be viable.
En effet, la faille CVE-2026-20841 exploite une injection de commande via des liens malveillants dans un fichier Markdown. Vous ouvrez le fichier, vous cliquez sur le lien, et hop, exécution de code à distance sur votre bécane. Personne chez M$ n'avait pensé à filtrer les protocoles des URL. Résultat, un lien du type file:///C:/Windows/System32/cmd.exe ou ms-msdt:// s'exécute comme si de rien n'était.
Rss feeds stehen im Footer im Bereich "Aktuelle Informationen". Warum nicht im <head> !?
Delete the Google Ad ID in the settings > Google > All services > Ads > Delete ID
The ambiguity level and the number of unknowns are definitely a crucial factor when it comes defining our modules, and especially when it comes to the implementation strategy choice
The more ambiguity we have, the more fluid and dynamic our domain is and the less certainty about its final shape we have, the more we should focus on adopting a strategy where it is the least costly to completely redesign and rearrange our modules.
Simple modular monolith: folders. Microservices needs one application per module. That's a high cost.
requirements, and some of them might have needs somewhere in between. Thanks to the fact that every module is now basically a separate application, we can assign different resources to each module and have it in a different, often dynamic, number of replicas, based on its own unique needs.
We can eliminate many problems of microservices by adhering to one, simple rule:
When serving any external network request, synchronous or asynchronous, a service can not make any network calls to other services, synchronous or asynchronous.
About SPAs: avoid global things that apply everyhwere
As the last resort, we can have a separate SPA per a few selected routes, having as many html pages as we have SPAs (multiple SPAs approach), or use the Micro Frontends
To reiterate, we went through the following strategies, ordered from simplest to the most complex one:
- Simple Modular Monolith
- Modular Monolith with Isolated and Independently Deployable Modules
- Modular Monolith with Helper Services
- Constrained Microservices - Microliths
- Microservices
I would say things are always easy when the modules are clear, defined and documented :)
Seeds data automatically for databases. It's marketing tells it's more automated than fakerJS.
Rust provides a single binary (lightweight compared to JS and more cache-efficient for Docker layers)
(via https://www.reddit.com/r/rust/comments/1r1emah/rewrote_my_nodejs_data_generator_in_rust_20x/ which seems generated by AI)
Zythom relate son utilisation de l'outil: https://zythom.fr/2026/04/pentests-assistes-par-ia/
It feels wrong to write HTML that way, but maybe I am too used to the HTML we daily use as web developer.
I like the research though.