med-mastodon.com is one of the many independent Mastodon servers you can use to participate in the fediverse.
Medical community on Mastodon

Administered by:

Server stats:

359
active users

#Scalability

1 post1 participant0 posts today
Replied in thread

@maikel basically, it boils down to the few key features of #Monero:

1. #Anonymity & #Privacy: Unlike with any other #cryptocurrency (aka. #Shitcoins) it's not just pseudonymous in that there is no mandatory linkage between individuals & their wallets, but the entire transaction history and balance is hidden. Unlike say #Bitcoin or #Ethereum one cannot track the coins from the moment of mining to their destination.

2. Speed: Monero's network does mine one block every 2 minutes. After 10 blocks any transfered balance gets unlocked for spending. That means that a transfer is completed at worst within 6 minutes and the balance is being unlocked at worst after 24 minutes. This makes it faster than Instant-#SEPA which only has a 1 hour SLA.

3. #Fungibility: Like #cash all it's coins are equal, since they cannot be tracked. This makes Monero the digital equivalent of cash.

4. #Scalability & #Stability: Monero adaptively self-adjusts block sizes and mining difficulty based upon demand (transactions in it's mempool aka. requested transactions that have to be added to the blockchain) and supply (total blockchain hashrate). Unlike Bitcoin and Ethereum it has a fixed Tail Emission Rate of at least 0,6 #XMR (Monero) per block, so the miners solving it get at least 0,6 XMR (+ transaction fees), which is a longterm stable rate. Bitcoin and Ethereum will necessitate huge transfer fees once their last coins are mined to make sense, which will result in the crash of said cryptocurrencies as they'll be too expensive to trade!

5. Anti-#ASIC and focussed on #CPU|s of general-purpose machines: Whilst it does run on #ProofOfWork, it's specifically designed to run poorly on #GPU|s and not on #ASICs as the latter one are not just manufactured #eWaste but also inherently increase the centralization (with less than a dozen big miners controlling >50% of Bitcoin and Ethereum's hashrate respectably). Thus it's the "least worst" in that regard. #ProofOfStake is not possible due to it's privacy-based setup (#Staking necessitates a public balance) and unlike a #Shitcoin like #FileCoin it doesn't incentivize #hoarding components. (in this case: #HDD|s)

6. Accepted & Convertable: Whilst there is a concerted effort to ban Monero, there are payment processors like #NowPayments that accept Monero. It's low transaction fees and good speed make it useable in settings like Restaurants and Online Stores (sadly not retail, because it would need to be like 60x faster)... And even then it's easy to convert to/from Shitcoins.

That's the #TLDW of Whiteboard Crypto, Mental Outlaw and The Hated One

And finally:

7. Monero gets continously developed and enhanced, whereas Bitcoin, #Litecoin and Ethereum don't even do proper #upgrades via #HardForks (see #EthereumClassic)...

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.

🏘️🤯 Control THOUSANDS of properties? Sounds impossible, right? Not with the right systems! I'm breaking down a scalable strategy for managing massive real estate portfolios in my latest #shorts video. Think streamlined processes, smart automation, and a whole lot of leverage. Check it out and let me know your biggest property management headache! 👇 youtube.com/shorts/WUOClZHbT7Y #propertymanagement #investing #scalability #business #automation #shorts #realestate

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 ... 😎

❇️ Unlocking #AI Potential with #Kubernetes & Key Benefits 🌐

Kubernetes is revolutionizing AI deployment with its scalable and efficient container orchestration capabilities.

Here are the key perks:
🔹Scalability: Automatically scales AI workloads to handle surges in demand, ensuring seamless performance.
🔹Efficient Resource Management: Optimizes CPU, GPU, and memory allocation based on workload needs, reducing costs.
🔹Multi-Tenancy: Allows multiple teams to share resources without interference, enhancing collaboration.
🔹High Availability: Ensures AI applications remain operational even during hardware failures, thanks to self-healing capabilities.
🔹Seamless Deployment: Enables consistent deployment across different environments, from on-premises to cloud.

klizos.com/kubernetes-ai-deplo

#Kubernetes #AI #MachineLearning #Scalability #Efficiency #MultiTenancy #HighAvailability #CloudNative #DevOps #CI/CD #ContainerOrchestration #ITInfrastructure #Innovation #TechTrends #CloudApplications #DataProcessing

❇️#Kubernetes in action: real-world #AI deployment success stories 🌐
Kubernetes is transforming AI deployment across industries with its robust container orchestration capabilities.

Some use cases:
🔸Netflix: Uses Kubernetes to simplify and streamline deployments, ensuring resilience and scalability for its vast array of microservices.
🔸HSBC: Manages applications across private and public clouds with Kubernetes, optimizing resource costs and meeting regulatory requirements.
🔸Airbnb: Orchestrates resources for complex machine learning models, ensuring efficient processing of large datasets.
🔸YouTube: Utilizes Kubernetes for scalable video delivery, handling spikes in demand without disrupting service quality.

klizos.com/kubernetes-ai-deplo

#Kubernetes #AI #MachineLearning #Netflix #GitLab #HSBC #Airbnb #YouTube #CloudNative #DevOps #Scalability #HighAvailability #CI/CD #ContainerOrchestration #ITInfrastructure #Innovation #TechTrends #CloudApplications #DataProcessing #RealTimeAnalytics #Automation

Kubernetes is revolutionizing how organizations manage complex applications, offering scalability, flexibility, and robustness.
Here are some more key use cases:
✅ Large-Scale Apps - Kubernetes helps manage large-scale apps during peak traffic, ensuring a smooth user experience.
✅ AI/ML with Kubernetes - NVIDIA uses Kubernetes to deploy AI models at scale, optimizing resource utilization.
✅ DevOps Efficiency - Spotify speeds up software delivery with Kubernetes, reducing time to market.
...

#Kubernetes #CloudNative #AI #MachineLearning #DevOps #Microservices #EdgeComputing #CloudNetworking #HybridCloud #Scalability #Flexibility #Reliability #CI/CD #ContainerOrchestration #ITInfrastructure #Innovation #TechTrends #CloudApplications #DataProcessing #RealTimeAnalytics #Automation #DigitalTransformation

acecloud.ai/resources/blog/kub

#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 comments”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 comments on LinkedIn
Continued thread

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 ProtocolFAQ - AT ProtocolFrequently Asked Questions about AT Protocol.

I've seen more people advocating for wider RSS adoption lately.

I was a heavy RSS user back in the day, but honestly, it’s a standard that struggles to keep up with modern demands.

In this short read, I break down why RSS’s pull model is inefficient and why push-based alternatives like ActivityPub are the future.

Read more: dev.to/justlig/rss-a-great-sta

DEV CommunityRSS: A Great Standard That Can’t Keep UpRSS (en.wikipedia.org/wiki/RSS) has long been praised as a decentralized, open standard for content...

The problems in the European Digital Identity (EUDI)

@jaromil's independent feedback on the dangers of the current #EUDI implementation. What it should be, and the issues it has regarding Fairness, Privacy, Security, Scalability, Obsolescence and Methodology.

#Fairness #Privacy #Security #Scalability #Obsolescence #Methodology.

news.dyne.org/the-problems-of-

News From Dyne · The problems in the European Digital Identity (EUDI)
More from Dyne.org foundation