The Snap initiative spearheaded by Canonical, Dell, Samsung, Intel, The Linux Foundation and others, enables a single binary to run securely on any Linux system (desktop, mobile, cloud, IoT - you name it) – a standard approach providing flexibility, simplicity, and security. Moreover, all of the various Snap-enabled applications need to communicate with a multitude of devices and systems. NATS is a messaging system all about simplicity, security, and performance. It’s a single binary with no external dependencies, and just a few MB in size. Read more...

Greta is a Swedish startup that wants to change the way content is delivered on the internet. Their team has developed a technology for peer-to-peer content delivery over webRTC, which uses NATS to create a rapid, highly scalable webRTC signaling system. Dennis Mårtensson , Co-Founder and CTO at Greta, will give an overview and answer questions, and we are excited to hear from him! Read more...

Introduction - Camel, NATS and Apcera Recently at Logimethods we’ve developed a new Camel-Nats component that can deploy on premise (non-cloud), and through the Apcera platform. In this blog, we’ll introduce this new component and explain why we believe that it was a critical missing link for organizations trying to develop an integration platform based on open source tools and cloud infrastructure. If you are not familiar with Apache Camel, a “Component” is another term for an adapter built using Camel framework. Read more...

NATS is about connecting different components: this allows you to test the components individually as well as their integration. As such, it’s essential to be able to generate and inject NATS messages. This is where a tool such as Gatling (an open-source load testing framework) is useful. The Missing Piece (Until Now) To generate and send messages to NATS, you could use the Java client for NATS (aka JNATS) by implementing your own Java code. Read more...

Speaker: Ryan Neal, Head of Infrastructure at Netlify When: October 19, 2016 11:00AM PDT Netlify is a platform for deploying high-performance websites and applications, serving up billions pageviews monthly for sites like: Uber, Vice Media, and Wikia to name a few. Ryan discusses why they selected NATS, his experience with NATS for Netlify’s data logging and control plane (for example using Logrus with a NATS hook , a connector for using NATS with Elastic , etc. Read more...

StrangeLoop began in 2009, as an event focused on distributed systems, security, emerging programming languages, and the like. This year nearly 1300 attendees came to StrangeLoop, and tickets were gone in less than 30 minutes after going on sale. Needless to say, StrangeLoop is one of the highlights of the calendar for anyone writing modern software systems. The focus is on interesting, original, and technical presentations, as the organizers explain: Read more...

I am in the process of launching a company I’ve founded in the IoT sensors space. I hope to be able to share more details very soon, but I wanted to share what I can in the meantime with the developer community about how we are using NATS in our IoT messaging initiatives and would be very interested in any feedback, suggestions or questions! Our platform is based on an IoT network of distributed sensors. Read more...

For those of you who might have read the previous post I did on Docker + NATS for Microservices , you’ll recall we took an in-depth look at using Docker Compose with NATS. That blog post was done a few days prior to DockerCon, and as expected Docker made many interesting announcements at DockerCon. One of the main things announced that week was Docker 1.12. 1.12 includes Swarm mode which can be used for assembling a cluster of Docker Engines and running workloads on them. Read more...

Some words about the Ariane project: While the DevOps trend is reducing application delivery time with automation on any step of the deployment, we still need to reduce the time to understand complex distributed applications: We still rely on hand-written technical documentations and diagrams; These documentations and diagrams are dispatched across teams (silo effect); The documentations and diagrams are also often not up to date (technical debt effect). Knowledge management is a key factor in reducing silo effect and improving the integration of new team members. Read more...

Speaker: Alberto Ricart, Principal Engineer, NATS When: August 30, 2016 Regardless of if you are interested in architecting an IoT network, moving a monolithic application to a microservices approach, or building cloud native applications, the majority of messaging systems were not designed with these paradigms in mind. Modern systems require a messaging infrastructure built for the scale, flexibility, and speed of today’s distributed systems. The webinar will cover: The basics of messaging patterns Why traditional messaging systems are not well suited for modern distributed systems What makes NATS different With that foundational info out of the way, we will lead into a fun demo inspired by Pokemon Go, showing how NATS could be use to enable real-time microservices at large scale. Read more...