5 publicaciones etiquetados con "architecture"

At plugNmeet, our goal is to provide a powerful, open, and flexible platform that adapts to your needs, not the other way around. As deployments grow and move to the cloud, managing media files like recordings and artifacts becomes a critical challenge. How do you store files in S3? How do you automate notifications when a recording is ready? How do you manage complex workflows in a multi-server cluster?

Until now, solving these challenges often required modifying the core application code, making updates difficult and maintenance a chore.

Today, we're thrilled to announce a powerful new feature that changes everything: Scripting and Storage Hooks. This new mechanism allows you to extend and customize plugNmeet's media workflow by executing your own custom scripts—either as efficient, long-lived processes or simple one-shot commands—at key stages. All communication happens via newline-delimited JSON over standard I/O, so you can integrate your own logic without touching a single line of the core code.

Your video service is a hit. User numbers are climbing, and engagement is high. But as you celebrate your success, a new problem emerges: your server bill is exploding. To keep up with demand, you keep buying bigger and bigger servers, paying a premium for resources that sit idle most of the day.

What went wrong? You've fallen into the monolith trap.

This post explains how Plug-N-Meet's modern, decoupled architecture is designed to prevent this exact problem, enabling you to scale your service efficiently and control your costs. For a business, this isn't just a technical detail—it's a core financial advantage.

When building any critical application, "scalability" and "high availability" (HA) are often top of mind. But for many, these terms conjure images of complex, multi-node clusters, expensive infrastructure, and a steep learning curve. The truth is, for most plugNmeet users, achieving both performance and resilience can be much simpler and more cost-effective than you might think.

This article will demystify the relationship between scalability and HA, and guide you through a pragmatic, phased approach to optimizing your plugNmeet deployment. We'll show you how to leverage the power of your cloud provider for HA, and why separating your recording server is almost always your first and best step towards true scalability.

We’ve all felt that moment of panic. You’re in an important online meeting, the chat is full of crucial links, and then you accidentally hit refresh. Everything is gone. To solve this, many applications store your entire session on their backend servers. This allows them to restore your session, but it comes at a huge cost: your sensitive data is now stored permanently on someone else's hard drive.

At plugNmeet, we believe this is the wrong trade-off. We've made a deliberate architectural choice to use your browser's own storage to provide a resilient experience without compromising your privacy.

Our philosophy is simple: if we don't need the data on our server to make the service work, we don't touch it.

Every great application is built on a foundation of smart architectural choices. For a real-time video conferencing platform, these choices are the difference between a smooth, reliable experience and a frustrating mess of lag, dropped calls, and connection errors.

When we designed plugNmeet, we had a clear set of goals: the platform needed to be high-performance, horizontally scalable, resilient, and easy for developers to build upon. This led us to make two fundamental decisions for our backend: we chose LiveKit for our media server and NATS for our real-time messaging layer.

This article is a deep dive into the "why" behind these critical choices.