Next steps post early access launch
By Jeffrey M. Barber
So, I launched and the next steps should be to go solicit people, hone my messaging, and try to get adoption. Fortunately, I have a few users, so my #1 priority it to support them. Unfortunately, I’m too embarrassed about the current of state of things and intend to focus on key technical limits. The key limit right now is the inability to scale up, and I’m perfectly happy to scale up without paying customers. Since I’m the largest customer of this infrastructure, I have to be happy.
I measured, got punched in the face, and I’m “early access” launching anyway.
By Jeffrey M. Barber
I love making plans, but…
Everybody has a plan until they get punched in the mouth. Mike Tyson
My problems started when I started load testing.
Open strategy for a new kind of business
By Jeffrey M. Barber
I’m nearing a launch of something which got me thinking about pricing. Pricing should ultimately reflect the values of the company which are in alignment with some kind of strategy. As freedom is a core company value, the best way to spread freedom is to lift all boats with rock bottom low prices. Unfortunately, low margins make for tough business. Fortunately, the infrastructure is only one aspect of the business strategy.
Deep Thoughts on Developing a Distributed Stream Query Language from the Ground Up
By Jeffrey M. Barber
As I type up my notes on the problems facing Adama, I’m thinking of how to integrate Adama within existing environments. A key problem for Adama’s future is that data held within Adama is currently very siloed. For board games and collaborative applications, this is perfectly fine. However, this can become problematic for many reasons. This is especially important for tactically migrating anything to Adama since developers need some degree of moving applications via a half-state.
Quick update on the march towards production
By Jeffrey M. Barber
Progress is being made, and things are looking good. Wanted to post an update on the march towards production
How I grew to hate PubSub; this one weird trick for building PubSub
By Jeffrey M. Barber
I’ve mentioned, in passing, that PubSub (i.e. the publisher subscriber pattern) over-commits, so I intend to dive into what I mean by this and talk about how I think about real-time services like PubSub. Having spent over half a decade as a technical leader for a very large (soft) real-time distributed system, I think it all boils down to this toy model.