Cohort Analysis ties Dave McClure’s, Eric Ries metrics for startups to real world tool. Excellent from Brett Slatkin.
Ordered key-value store superceeds relational SQL?
3 reasons SQL Server is past its peak.
1 - The economics of SaaS don’t pencil out. Moving forward SaaS companies without big data partnerships are doomed to low profits.
2 - SQL Server is unable to evolve on its own to support big data partnerships, hence Microsoft’s Hadoop partnership with Horton Works.
3 - Small companies need to belong to networks to collaborate and gain certainty of demand.
Developing on SQL Server you quickly learn the more relationships between tables the lower the ability to distribute the system and scale up. I’d also claim code becomes ossified and bound to the database making applications dated.
Consider a different approach using Order key-value store with Blueprint allowing multiple data elements to be updated in a single transaction
The Blueprints layer illustrates the power of FoundationDB layers. Our core database combines an ordered key-value store with multikey ACID transactions, allowing multiple data elements to be updated in a single transaction. By mapping higher-level data elements to key-value pairs, a developer can write small amounts of code to implement a rich data model.
Touch Bionics prosthetic app gives the wearer greatly expanded control capability via 24 Quick Grip. Google Glass, wouldn’t it be better than an app?
