Wrote a blog on why AWS never dove seriously into blockchain. Features groovy pix from a trip to New York, which is part of the story: tbray.org/ongoing/When/202x/20

@timbray interesting that QLDB also launched and didn’t make it as a mainstream service. I think it was too hard to market it to the right people and those that might be interested wanted something more portable.

@adrianco If QLDB had been more like internal QLDB, with appliers and so on, it should have found an audience. I was baffled when it turned into something else that I could never really understand.

@timbray @adrianco I was super excited when QLDB launched, then majorly disappointed to find out it wasn't *that* (the internal) QLDB.

@timbray @adrianco we’re currently using it but wondering if we will migrate to a ‘regular’ db with tight permissions instead.

@onyxraven @adrianco I think it's a perfectly decent project, just shared a name with an internal thing that was quite different.

@timbray @onyxraven I think it would have been much more successful if it had been open sourced as part of the launch. I agree that making closer to the internal service would also have helped get it out quicker and got more use from ex-Amazon devs who understood what to use it for.

@adrianco @timbray ya I think maybe it’s in between use cases in its current form. Auditable data version log is great, but the trade offs are a little steep on its own.

Sign in to participate in the conversation

Everyone is welcome as long as you follow our code of conduct! Thank you. Mastodon.cloud is maintained by Sujitech, LLC.