Future plans include reducing structure memory overhead, making transactions computationally “free”,
and further Lua runtime performance improvements
By supporting StructD, you ensure that our future plans are fulfilled, and that those changes become
Paying customers’ votes get more weight for future improvements to StructD
Why does purchasing a license allow me to run 2 production + 2 non-production? Why isn’t the price half for
half as much? Why don’t you license production vs non-production separately?
StructD Commercial Edition is intended to be used by companies who want to use Structd or a
Redis-protocol compatible daemon. Nearly all interesting uses of StructD (or Redis) that the authors
have been involved with required at least one master and one replica in production, at least one shared
development / testing instance, and at least one staging instance. We give you everything you need for
that very standard setup with one license.
Smaller setups than two production instances don’t need the performance enhancements that are
highlighted in the commercial edition of StructD, and would likely be better served by the open source
edition available at structd.org
Reducing the cost of a license and giving you fewer rights per license only means that 99% of customers
buying a license will be buying 2+, or will buy 1, then come back 2-6 weeks later to buy a 2nd license.
Trying to convince 99% of customers to select ‘2’ instead of ‘1’ is silly, so we don’t. Instead, we
include what you actually need right up front.
The included non-production licenses are meant to allow you, the developer, customer, and user of
StructD Commercial Edition to be able to build software using the same tools in development as in
production. Our accountants tell us that keeping our production + non-production install per license in
parity helps prevent license abuse. We hope that our customers are so happy with the product, they see
the license fee and smile, because of the money they save.
Can we get a site license for non-production StructD instances?
Dr. Josiah needs transactions and other improvements to a Redis-like daemon
Salvatore doesn't want transactions with rollbacks in Open Source Redis
Seems we are at an impasse
To get transactions with rollbacks, along with other improvements that Dr. Josiah needs for his work, a
fork was necessary
To ensure that those further changes make it into StructD, it is being commercialized.
Why are you commercializing StructD?
Dr. Josiah’s experience in giving away software has netted him little in 16 years, but has otherwise
found success writing software and mentoring for a variety
of ~SiliconBeach, CA startups
Dr. Josiah and his team can spend their days working for someone doing something else, with evenings
and weekends trying to make what Dr. Josiah needs StructD to be, or we can try to commercialize our
improvements, which may be what others need.
All of StructD is intended to be open source long-term, though changes slowly percolate from our
commercial edition to the open source edition due to development priorities. Want us to devote more
time? Get a support package, and vote! Or don’t use StructD out of principle, and hope that someone
else will support the StructD team enough to make sure that everything goes open source before the
Each of our products / services has a “cost” for us to deliver that product / service. We charge above
that cost to generate a “net” revenue per sale of a given product / service. Part of our “be a
responsible member of the community” plan is to donate portions of our net revenue per sale to open
source projects that are either direct ancestors of code of StructD, or to open source authors in the
community that we think should be supported.
Who is Dr. Josiah?
Dr. Josiah Carlson Ph.D. is an American Theoretical Computer Scientist, best well known for
his book on Redis; Redis in
Action, his talks on Redis and/or Python, his open source libraries relating to Python,
Redis, Lua, thousands of public mailing list posts relating to Redis, Python, wxPython, and/or data
compression, as well as a handful of blog posts relating to the same. Professionally,
the good doctor has worked on email anti-spam, text search, non-binary classification, GPS navigation, data
compression, streaming video, social networks, web ads, database technology, business finance, and ETL
pipelines. In open source, Josiah offers libraries for timezone-aware cron libraries in Python, a
SQLAlchemy-like object layer for Redis , a task queue scheduler, and more.
Dr. Josiah has given talks at LADevOps August 2011, LAWebSpeed 2012, Redisconf 2012 and 2015, Postgres Conf
2012, Py Data Science LA meetups January 2017 and December 2017, and sat on an Entrepreneurship panel at
AWS re:Invent 2012.
If you would like to see Dr. Josiah give a self-introduction, where he discusses some of his work personally
and professionally, you can watch
him here. Or you can see some of his public / personal work at
his blog, or professional work at LinkedIn.
This page and its contents are Copyright 2019 NISR LLC, All rights reserved.
The StructD name and logo are a registered Trademark of NISR LLC.