Jan Plutzer

Great to be on the '30 Startups to Watch in 2024' list from DBTA 🌟 "Innovation in the big data and analytics space continues to blossom, with more companies than ever before riding the high of generative AI" dbta.com/Editorial/News…

@puneet324 @derekcollison @synadia Thank you Puneet and @trueventures for all your support - exciting times ahead.

Congrats @derekcollison @jan_plutzer and the incredible @synadia team + community. Excited for all that comes next

I wish Biden would come out and say he wants Trump on the ballot. The 14th doesn't apply. Then thanks him for the playbook describing how to never leave office and the appreciation of knowing he can't be charged, no matter what he does. And ends it with " My Fellow Americans , I'm not ever going to leave the White House and there is nothing you can do to me. " Which would confirm exactly why SCOTUS will keep Trump off the ballots and why Trump will never get immunity

The best shoutout for a contribution ever. Nice 😎

Manage the power of #NATSio easily with Synadia’s newest offering — 💫 Synadia Cloud

Just a reminder that on the 12/27/20 phone call where Trump told the acting Attorney General & his deputy to "just say that the election was corrupt and leave the rest to me & the R. congressmen," Trump also singled out one of those members, a "fighter" named Jim Jordan. 1/

Thanks for including #NATSio!! 👏

Latest article at the link on my profile. Untangling the Legacy Web: A Fresh Approach to Smarter Choices Stepping into a forest of legacy enterprise systems as the newly minted enterprise architect can be daunting. Imagine being handed a map to a labyrinth, where every turn reveals a new layer of decisions made by well-intentioned predecessors. Our current environment is a vibrant tapestry woven from MassTransit, NServiceBus, MSMQ, and Azure Service Bus threads. Some of these systems have served their purpose, but now it's time to weave a new narrative. We're not here to point fingers or assign blame. These systems were likely the right choices at the time and have been instrumental in our journey thus far. But just as a snake sheds its skin, we need to shed our old systems to allow for new growth. Enter @nats_io, our potential path out of the forest. NATS is the Marie Kondo of distributed systems. It promotes simplicity, allowing us to build a solid foundation and then, if needed, layer complexity on top. It's perfect for quick, lightweight connections but can also shoulder the weight of full-scale, reliable solutions. And the best part? It doesn't demand exclusivity. We can keep using other solutions that still make sense. Here's our evolving game plan as we embark on this journey: - We bid adieu to MSMQ. It's been a reliable ally, but its time has come. - The NATS client can run anywhere our legacy clients can, providing a smooth path forward for everyone. This will ensure our older apps can transition smoothly when they're ready, irrespective of the side of the message they're on. - Azure Service Bus isn't packing its bags. It remains a viable option for teams that are comfortable with it. For our critical systems, we'll continue to rely on NServiceBus and pay the luxury tax. NATS will serve as the backbone and bridge that can accommodate on/off ramps and cross-bus communication, if necessary. It's worth mentioning that navigating politics and risk aversion can be as challenging as any technical issues. As we begin to establish a stronger reputation for our system and showcase the benefits of our evolved event-based architecture, we'll be in a position to leverage NATS for bigger and better things. That's why we're starting with NATS as our bridge before making any sweeping decisions about migrating away from one technology or the other. This is just the beginning of our journey. As architects, we don't claim to have all the answers upfront, but we're committed to making informed, intelligent choices for our architecture. As I navigate this maze of legacy systems, I'll attempt to shed light on the "why" behind our architectural decisions, documenting our steps, successes, and stumbles along the way. So, stay tuned for the next installment in our ongoing saga!

@derekcollison @nats_io Derek, you're just as sharp as you were in 2010, actually even more so, which is the highest praise I can think of :-) So happy to see NATS thriving.

Power up your NATS deployment with Synadia Control Plane, out now! Secure, Manage, and Observe #NATSio at scale - Self-Hosted and Private SaaS available. synadia.com/blog/announcin…

@brianflannery @gwenshap @d_feldman @Memphis_Dev @nats_io @synadia 💯

@gwenshap @d_feldman @Memphis_Dev Definitely check Look at @nats_io , lmk if want to sync further on it sometime. our team at @synadia is building tooling for it as well, and our founder created NATS.

Now that I'm thinking about job queues, I don't think I have a solution I'm 100% happy with. - RDBMS doesn't scale well - Kafka is a mismatch in APIs and data model - RabbitMQ was a bit of a DR nightmare last I tried Anyone has OSS queue that scaled to 100K+ workers?

@alexjc_eth @stevanzetti @RepSwalwell And preserving deposit amounts doesn't involve taxpayers.

I’m working with my CA colleagues to address the Silicon Valley Bank crisis. We must make sure all deposits exceeding the FDIC $250k limit are honored. Banking is about confidence. If depositors lose confidence on the safety of their deposits over 250k then we are in trouble.

@ericabrescia 😟

Welp, someone already trying to hack my twitter account right now after the SVB / VC tweet...

Have to say that I am super impressed with the level of effort @synadia puts into developer relations with @nats_io. They have built an active community and are generating some really engaging content. Check out this newest video from @thecodegangsta! youtube.com/watch?v=byHGNU…

gRPC over Nats is an excellent combination, very simple, but scales out massively, doesn’t require service mesh, makes micro services comms like a cakewalk. Running our services more than a year now using nats as our major backbone, thanks @nats_io

Thanks for being a #NATSio fan! 😍 Check out this quick read from ⁦@flydotio⁩ Global Deployments in Sync · Fly fly.io/laravel-bytes/…

The top 3 things in open-source I'm pumped to use this year: 1⃣ Bun by @jarredsumner 2⃣ NATS JetStream by @synadia 3⃣ Expo Router by @Baconbrix [1] bun.sh [2] docs.nats.io/nats-concepts/… [3] expo.github.io/router/docs

🥳 Today is the Day!!! Just a few hours away and we can’t wait to see everyone at RethinkConn 2022 — You can still register to join us for this free virtual event!

Jeremy Saenz and Todd Beets from Synadia gave a great presentation about using NATS to simplify communication everywhere. #KubeCon #Kubernetes #CloudNativeNA #KubeConNA #CloudNativeCon #OpenSource #K8s

NATS: You Need it Now! cncf.io/blog/2022/10/0… #cncf via @CloudNativeFDN If you need pub/sub features in your #Edge or #distributed service, it's worth having a deep look at @nats_io, easy to deploy, efficient, resilient, and secure implementation. 😉