Showing Post From Architecture
Internal tool builders in 2026: revisit Appsmith, ToolJet and Budibase before you build another admin panel
Every growing company ends up with a second, quieter product: the screens its own staff use. Support needs to look up an order and resend an invoice.
Read moreWorkflow automation in 2026: revisit n8n, Node-RED and Activepieces before you wire another business process to a webhook
Most teams first meet workflow automation as a shortcut: draw a few boxes, point a webhook at a SaaS, and declare the process automated.
Read moreData catalogs in 2026: revisit OpenMetadata, DataHub and Apache Atlas before you add another metadata platform
Most teams do not decide to build a data catalog. They drift into needing one. A new analyst asks which of three “orders” tables is the real one.
Read moreStatic code analysis in 2026: revisit Semgrep, Opengrep and SonarQube Community Build before you add another code scanner to CI
Most teams add a code scanner to CI in an afternoon. A YAML job, a default rule pack, a green tick.
Read moreSchema registries in 2026: revisit Confluent Schema Registry, Apicurio Registry and Karapace before you ship another event schema
An event schema looks harmless in a pull request. A few fields, a namespace, maybe a default value. But once a producer starts writing with it, that schema is a contract with every consumer that reads the topic today and every consumer that will replay it next year.
Read moreKubernetes storage in 2026: revisit Rook-Ceph, Longhorn and OpenEBS before you put another database on a persistent volume
Running stateless services on Kubernetes is routine now. Running state is where the calm ends. The moment a database or a file store asks for a PersistentVolumeClaim, somebody must answer: where do those bytes live, how many copies exist, and what happens when a node dies at 2 AM?
Read more