Konto erstellenAnmelden

Frühere Suchanfragen

Keine früheren Suchanfragen

Suchoptionen

Nur verfügbar, wenn angemeldet.
sueden.social ist einer von vielen unabhängigen Mastodon-Servern, mit dem du dich im Fediverse beteiligen kannst.
Eine Community für alle, die sich dem Süden hingezogen fühlen. Wir können alles außer Hochdeutsch.

Verwaltet von:

Serverstatistik:

1,9 Tsd.
aktive Profile

sueden.social: ÜberStatusProfilverzeichnisDatenschutzerklärung

Mastodon: ÜberApp herunterladenTastenkombinationenQuellcode anzeigenv4.3.8

#scalability

1 Beitrag1 Beteiligte*r0 Beiträge heute
Öffentlich
Yuna

Is Node.js the future of backend development, or just a beautifully wrapped grenade?

Lately, I see more and more backend systems, yes, even monoliths, built entirely in Node.js, sometimes with server-side rendering layered on top. These are not toy projects. These are services touching sensitive PII data, sometimes in regulated industries.

When I first used Node.js years ago, I remember:
• Security concepts were… let’s say aspirational.
• Licensing hell due to questionable npm dependencies.
• Tests were flaky, with mocking turning into dark rituals.
• Behavior of libraries changed weekly like socks, but more dangerous.
• Internet required to run a “local” build. How comforting.

Even with TypeScript, it all melts back into JavaScript at runtime, a language so flexible it can hang itself.

Sure, SSR and monoliths can simplify architecture. But they also widen the attack surface, especially when:
• The backend is non-compiled.
• Every endpoint is a potential open door.
• The system needs Node + a fleet of dependencies + a container + prayer just to run.

Compare that to a compiled, stateless binary that:
• Runs in a scratch container.
• Requires zero runtime dependencies.
• Has encryption at rest, in transit, and ideally per-user.
• Can be observed, scaled, audited, stateless and destroyed with precision.

I’ve shipped frontends that are static, CDN-delivered, secure by design, and light enough to fit on a floppy disk. By running them with Node, I’m loading gigabytes of unknown tooling to render “Hello, user”.

So I wonder:
Is this the future? Or am I just… old?

Are we replacing mature, scalable architectures with serverless spaghetti and 12-factor mayhem because “it works on Vercel”?

Tell me how you build secure, observable, compliant systems in Node.js.
Genuinely curious.
Mildly terrified and maybe old.

Compiled Languages vs NodeJs picture
#NodeJS#BackendSecurity#SecureCoding
Öffentlich
Felix Palmen :freebsd: :c64:

First change since #swad 0.2 will actually be a (huge?) improvement to my #poser lib. So far, it was hardwired to use the good old #POSIX #select call. This is perfectly fine for handling around up to 100 (or at least less than 1000, YMMV) clients.

Some #select implementations offer defining the upper limit for checked file descriptors. Added support for that.

POSIX also specifies #poll, which has very similar #scalability issues, but slightly different. Added support for this as well.

And then, I went on to add support for the #Linux-specific #epoll and #BSD-specific #kqueue (#FreeBSD, #NetBSD, #OpenBSD, ...) which are both designed to *solve* any scalability issues 🥳

A little thing that slightly annoyed me about kqueue was that there's no support for temporarily changing the signal mask, so I had to do the silly dance shown in the screenshot. OTOH, it offers changing event filters and getting events in a single call, which I might try to even further optimize ... 😎

kqueue client code, manually relaxing the signal mask for just the single kevent() call waiting for new events.
#C#coding
Öffentlich
Syde

🎤 How Open Source Powers the Enterprise – Yesterday, our Commercial Director Ronny Marx took the stage at #CloudFest to share why WordPress is made for enterprise companies. 🚀

43% of all websites run on WordPress – meaning nearly every second website you visit is powered by it! He also showcased real-world cases proving that WordPress is both scalable and secure. 🔐 🌍

Ronny Marx stands inside a boxing ring-style stage at CloudFest, holding a microphone while presenting. Above him, two large screens highlight a key statistic: ‘43% of all websites run on WordPress,’ reinforcing the scalability and security of the platform.
large audience watches Ronny Marx, Commercial Director at Syde, giving a talk on an elevated stage designed like a boxing ring at CloudFest. The event setup includes a professional lighting rig and multiple banners from sponsors.
Ronny Marx, Commercial Director at Syde, speaks on stage at CloudFest, presenting in front of a packed audience. A screen above him displays the WordPress logo, emphasizing the talk’s topic on Open Source and enterprise solutions.
#CloudFest2025#WordPress#OpenSource
Öffentlich
Coach Pāṇini ®

#Scalability is a product of a rational and production oriented view of the world, tied to ideas of resource extraction, leverage, and production to get ”more”.
linkedin.com/posts/fridgren_so

www.linkedin.com”Sorry, love the idea, but it doesn’t scale” I’ve got three children. And… | Daniel Fridgren | 22 Kommentare”Sorry, love the idea, but it doesn’t scale” I’ve got three children. And in a way, you could say they are the core of my investment portfolio. I invest a lot of time and resources in them. They are lousy business ideas from a scaling viewpoint. There will be no hockey sticks. No 100x returns on investment in regular business terms. They won’t scale. And that is precisely the point. I don’t want nor expect scalable returns. The output that matter to me is not even measurable. And if all things go the way I’d like it to, I won’t even be around to see the full extent. The most important things in life doesn’t scale. Scalability is a product of a rational and production oriented view of the world, tied to ideas of resource extraction, leverage, and production to get ”more”. More of what? Hollow gains? What truly matters cannot scale. Yet, scalability is of major importance for investors. It is often celebrated in technology and business contexts as a way to maximize efficiency and impact. Impact? Of what kind? ”We only look for scalable solutions for this problem.” ”If we can standardize this, the TAM will be huge.” ”The network effects here gives financial leverage.” So when we scale, what do we loose? Depth. Automated customer service may be scalable. But often the experience is subpar to talking with a real human. Variation. Scalable solutions tend to flatten out local and cultural variation. Homogeneity is often a result in the hunt for scalability. Robustness. What’s scalable in terms of human enterprises is often centralized and with single points of failure. Fragile. There is a vast number of non-scalable investments out there with great payoff. By funding and nurturing what’s not scalable, we gain in many important areas. Some of which are: Antifragility. Depth. Variability. But funding that which doesn’t scale has mostly been left to countries—and to a smaller extent charities and NGOs. Given our outlook today, I believe we need to revisit this strategy. The corporate layer most of us are working within resides on top of another layer which is often forgotten. This layer is a foundation that itself has a core of non-scalable investment, essential to human dignity and social cohesion. Just like externalized costs, it is not accounted for. Could it be that there is a systemic risk in not being more interested in this layer from a corporate standpoint? With very few exceptions, corporations today do not care much about it. Mondragon is the only real exception I have found so far. The rug pull will be rough if the foundational layer goes south. And who knows how long the idea of countries will persist. It may be time to start to invest more in the non-scalable, and support alternative, resilient structures that are able to alleviate the outcomes if nations aren’t able to support anymore at some point in the future. What is a non-scalable investment your corporation could do? | 22 Kommentare auf LinkedIn
Antwortete im Thread
Öffentlich
☮ ♥ ♬ 🧑‍💻

Big question, Why ATProtocol from #BlueSkySocial #PBC’s mouth instead of Mastodon and ActivityPub?:

“Why not use ActivityPub? #ActivityPub is a federated social networking technology popularized by #Mastodon.

Account #portability is a major reason why we chose to build a separate protocol. We consider portability to be crucial because it protects #users from sudden bans, server shutdowns, and policy disagreements. Our #solution for portability requires both signed data repositories and #DIDs, neither of which are easy to retrofit into ActivityPub. The migration #tools for ActivityPub are comparatively limited; they require the original server to provide a redirect and cannot migrate the user's previous data.

Another major reason is #scalability. #ActivityPub depends heavily on delivering messages between a wide network of small-to-medium sized nodes, which can cause individual #nodes to be flooded with traffic and generally struggles to provide global views of #activity.”

Short version, WE CANT CONTROL YOU.

<atproto.com/guides/faq>

AT ProtocolAtproto Ethos - AT ProtocolA deep dive into the philosophical and aesthetic principles underlying the design of AT Protocol.
Öffentlich
Yuna

💡 Resilience. Reliability. Reusability.
Always wrong investments…

If you think bugs, tech debt & maintenance are “normal,” do the world a favor: resign. You’re part of the problem.

MVP/PoC ≠ Done.
It’s a candle - fragile, short-lived.
Real engineering = the light bulb: robust, lasting.

But devs & managers stop at "it works."
Why? Because real engineering demands more.
More thinking. More iterations. More uncomfortable truths.

💀 Fragile systems = endless maintenance.
💀 Seniors wasted on babysitting.
💀 Knowledge stagnates.

🔍 Product & Tech - Two worlds, but only one is visible.
Mixing them = slower, costlier, dumber.

🔥 Resilient systems don’t break.
🔥 Reliable systems don’t fail.
🔥 Reusable systems don’t get rewritten.

Start building like you mean it.

Pigs proudly celebrating their straw triumph while the inevitable storm begins its demolition
#Engineering#TechDebt#Resilience
EntdeckenLive-Feeds
Über