Thanks to everyone who participated live and on-line in our recent investor Q&A webinar! We had a great turnout, and we hope you enjoyed the information shared. 

If you missed last week’s event, we’ve provided a recording  of the webinar for you to watch at your earliest convenience. We’ve also highlighted some of the important questions that were addressed directly in this article!

Compressions Been Around for 50 Years. What’s the Problem?

The problem is with machine generated data, IoT data, internet of things, is that data is, the file sizes are really small. They can be a hundred bytes, 10 bytes, five bytes, they are really tiny compared to a megabyte or even a few kilobytes, a typical file for which you can use compression. 

The problem is the way compression works; it works on one file at a time. So, if you’re trying to find repetitions of pattern on a file, one file, you’re not going to find very many if the file is tiny. It’s just too small to find patterns that repeat, which is the key requirement for compression to reduce the size of it. And so because it doesn’t work on these small files, compression just doesn’t get used in IoT data, unless you’re putting a lot of it together in a process called batching, which means basically you wait until the messages add up to enough to use compression – that means you are not getting the data in real time. It could be minutes or hours of latency, which is pretty problematic for most users.

When you compare us to batching with compression, we can run 400 times faster – and that’s provable mathematically – at a typical reduction of 75%. We’ve seen it over and over. And that combined with a light compute means that we effectively quadruple the bandwidth on average, for virtually any connection.

New Features? When Will They Be Up and Running?

“Our Chief Science Officer, Josh Cooper, has a prototype of our new combination of compaction and encryption, a major project, up and running, but it’s not close to a release. It has to go through all sorts of testing, documentation, and refinement. I don’t want to be held to a release date because it depends on having the resources and the financial means to get people involved to do all the testing and refining. 

If we had those resources right now, definitely before the end of the year. The full resources are not there yet, so progress will be slower.”

You Had a Successful First Raise… Why Another One?

We need more money, and we need more engineers. I mean, you have to think about how much it costs to hire an engineer – you can see what I mean. The average pay at Google, including the guys who serve lunch, is $250,000 a year. We don’t pay that much, of course, but doesn’t take very many engineers to add up to boatloads of money. And I can tell you, not much of that money not going to me.

How Can I Invest in AtomBeam?

We’re glad you asked! As you may know by now, AtomBeam is currently raising funds through an equity crowdfunding campaign on StartEngine.

We’ve already raised over $5M and encourage you to join us as we revolutionize the way we view data transmission. Head over to our raise page to learn how you can be a part of our rapidly growing investor community today!

Leave a Reply

Your email address will not be published. Required fields are marked *