Next big thing will of course be an Ai implementation!
www.zooml.dev
This will not finish the diagram for you - but provide analysis of the diagram you have provided!
Verwaltet von:
#systemarchitecture
0 Beiträge0 Beteiligte0 Beiträge heute
Now its possible to see a small preview of your diagram, making it easier to identify the diagram you're working on!
Antwortete im Thread
@mjglopez Definitely a combo of #1 and #2: Been working #refactoring truly enormous amount of code for the last years, code which has its oldest roots from 2003. It has been a great learning experience while having the chance to restructure large sections of the #systemarchitecture Painpoints? Sure. But what cool results, improved #performance and first of all: #maintainability
... This is where your diagram will live! <3
Now its possible to have 5 diagrams in cloud storage! (the local storage is still available if you're not logged in)
New implementation of the userflow. Decided to have all the edits in a sidebar to make it easier to change.
tried to model a simple controller in my diagram tool
Got great feedback from a user of ZoomL. So now it possible to search through all the classes in the diagram!
+ <<readonly>> <<supersecret>> key: guid
have multiple visuals in my new DCD tool
Antwortete im Thread
It's an interesting point you highlight because I've never thought of things through that paradigm. Now that I see it, I realise I'm hoping to transition to #openBSD because I believe of mainstream operating systems, it probably has the best #DX.
In this particular case, I believe that the developers exploit that in order to optimise for what might be called #security which impresses me.
I realise it's probably an outlier in this regard!
Here is a video of how the interaction with the new classes will work, from next week!
The latest update will arrive on tursday next week!
There's a new stylish update along with some nice to have features such as copy paste.
Doing a major visual overhaul of the design class diagram im making
Recently, while working on a workshop titled Testing Your Pull Request on #Kubernetes with GKE, and GitHub Actions, I faced twice the same issue: service A needs service B, but service A starts faster than service B, and the system fails. In this post, I want to describe the context of these issues and how I solved them both with the same tool.
Are you a senior software developer, architect, or engineering leader wrestling with performance bottlenecks and increasing system complexity?
This #InfoQ talk, based on Aleksey Shipilev's performance work phase diagram, reveals the critical "Performance - Complexity Curve" and how it impacts your engineering decisions and costs.
Watch the video now: https://youtu.be/0tSLRAPC_0M
Design Principle: Minimize Dependencies — https://sleepingpotato.com/design-principle-minimize-dependencies/
#HackerNews #DesignPrinciple #MinimizeDependencies #SoftwareDesign #BestPractices #DeveloperTips #SystemArchitecture
Sleeping Potato · Design Principle: Minimize DependenciesWhen I started building the base framework for Looping, I defined a set of design principles to guide its development. Establishing these principles from the start helped refine my thinking, avoid implementations that felt "off," and encourage simplicity, abstraction, and reusability for long-term maintainability.
One of those core principles is
Understanding System Abstractions for LLM Integration
https://www.jocheojeda.com/2025/02/23/understanding-system-abstractions-for-llm-integration/
Scalable architectures, two concepts: 𝙎𝙘𝙖𝙡𝙚-𝙐𝙥 𝙖𝙣𝙙 𝙎𝙘𝙖𝙡𝙚-𝙊𝙪𝙩
But when to use one over the other?
In this blog post, our very own @noctarius2k, wrote about the pros and cons of each of the approaches. Simplicity and limited scalability vs complexity and higher scalability.
He also explains how simplyblock is implemented and why we did what we did 
Link to the full blog post: https://www.simplyblock.io/blog/scale-up-vs-scale-out/
How to build a highly available, multi-regional scheduler using AWS services, ensuring at least one delivery policy for critical workflows:
https://softwaremill.com/building-a-multi-regional-highly-available-scheduler-with-aws/
SoftwareMillBuilding a multi-regional, highly available scheduler with AWSHow to build a highly available, multiregional scheduler using AWS services, ensuring at least one delivery policy for critical workflows.
This discussion on HN about why you may not need anything other than Postgres: https://news.ycombinator.com/item?id=42036303
brings up a good question about Redis- one I've wondered myself: Are we using Redis the wrong way?
The main use of Redis is as a simple key/value store. The idea is that if we are doing a process such as a DB query, we can cache the result. This is essentially memoization, and I remember this being used way back with a program called memcached.
Redis is a highly optimized key/value store, but many people (myself included) use hosted Redis servers. This introduces a lot of overhead on reads.
Wouldn't we be better off moving the key/value pair server as close to the application as possible, and then relying on writes being distributes to all instances? At worst we might get old data, but if we're using the system for caching, that shouldn't matter much, and we can instead rely on eventual consistency.
I'm curious as to other's thoughts on this.
news.ycombinator.comDo you need Redis? PostgreSQL does queuing, locking, and pub/sub (2021) | Hacker News