View profile

Big money for Redis Labs and big controversy over Facebook's React licensing

On a pretty slow news day, here are the three things that really stuck out to me: 1. Redis Labs raise
Big money for Redis Labs and big controversy over Facebook's React licensing
By ARCHITECHT • Issue #125 • View online
On a pretty slow news day, here are the three things that really stuck out to me:
1. Redis Labs raises $44 million: Redis is, of course, a very popular in-memory, open source, key-value database. And Redis Labs appears to have a strong business selling enterprise versions of the software, as well as running a managed cloud service. I like the way the company handles its open source business model, by building a relatively simple technology that can grow a large user base, and then not hesitating to productize it. 
By the way, it seems almost like a forgone conclusion that all database startups will eventually offer managed cloud versions now—although that certainly was not the case years ago. I’m curious how much strain it puts on smaller companies to maintain and support a technology across open source, enterprise and cloud versions.
2. Facebook is getting flak for its React license: It’s tough to tell if this is much ado about nothing, but back in July the Apache Software Foundation blacklisted Facebook’s React license (which is called BSD + patents) because ASF didn’t like its terms, which allow Facebook to revoke users’ rights to the React patents if they file a patent claim against Facebook. The patent claim does not have to relate to React. And by “blacklisted,” I mean disallowed ASF projects from including dependencies on technologies using that license.
Facebook blogged about the ASF’s decision on Friday, which led to several blog posts, including this really good one explaining what’s up and why it matters. Essentially, it’s a question of whether Facebook is right to try and protect itself from patent lawsuits, whether this is the best way to do it, and then whether the mass adoption of this practice would kill open source. It’s not hard to see how it could at least chill adoption and encourage large companies to just build their own software (or, perhaps, buy it).
3. Facebook details its edge networking infrastructure: Speaking of Facebook, it knows a thing or two about infrastructure when it’s no busy upsetting open source users ;-) And on Monday it published a blog post (and an academic paper) discussing how its Edge Fabric manages traffic flow from users’ devices to Facebook’s data centers. 
Obviously, Facebook’s traffic demands are beyond what most companies will ever face, and content networks are different than computing platforms, but this an interesting read nonetheless. Other companies will have to start thinking about their own edge infrastructure, too—especially if they plan on getting into latency-sensitive areas like IoT and AI. Most won’t build anything on par with what Facebook is doing, but there are interesting options emerging from cloud providers, telcos and even startups, like Vapor.

Sponsor: Bonsai
Sponsor: Bonsai
Listen to the latest ARCHITECHT AI Show
Artificial intelligence
Sponsor: DigitalOcean
Sponsor: DigitalOcean
Cloud and infrastructure
If you enjoy the newsletter, please help spread the word via Twitter, or however else you see fit.
If you’re interested in sponsoring the newsletter and/or the ARCHITECHT Show podcast, please drop me a line.
Use Feedly? Get ARCHITECHT via RSS here:
Did you enjoy this issue?

ARCHITECHT delivers the most interesting news and information about the business impacts of cloud computing, artificial intelligence, and other trends reshaping enterprise IT. Curated by Derrick Harris.

Check out the Architecht site at

If you don't want these updates anymore, please unsubscribe here.
If you were forwarded this newsletter and you like it, you can subscribe here.
Powered by Revue