How NoSQL forced the evolution of a scalable relational database
I think NoSql, especially things like Mongo, got popular because it is super easy to program with javascript.  While scaling is one of the advantages, I&#x27;d be super surprised if many people actually need scaling capabilities ( other than because their design is super inefficient ).<p>Recently I&#x27;ve been inspired to play around with kicking out as many layers between a relational db and a REST Api, largely because I&#x27;ve been watching <a href="https:&#x2F;&#x2F;www.twitch.tv&#x2F;nybblesio" rel="nofollow">https:&#x2F;&#x2F;www.twitch.tv&#x2F;nybblesio</a>  ( who I first came across here on HN on a thread about live coding via twitch streaming ).   One of his projects he works on is a SASS product which is largely done in postgresql leveraging  <a href="https:&#x2F;&#x2F;github.com&#x2F;PostgREST&#x2F;postgrest" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;PostgREST&#x2F;postgrest</a>  .  Seems pretty good, going to be interesting to see how it turns out   ( though I haven&#x27;t seen him work on it lately )<p>I tend to like SQL Server, ASP.NET Core and found <a href="https:&#x2F;&#x2F;blogs.msdn.microsoft.com&#x2F;sqlserverstorageengine&#x2F;2018&#x2F;01&#x2F;29&#x2F;simplify-rest-api-development-modern-single-page-apps-sql-server&#x2F;" rel="nofollow">https:&#x2F;&#x2F;blogs.msdn.microsoft.com&#x2F;sqlserverstorageengine&#x2F;2018...</a>    and I&#x27;ve been playing around with this kind of idea and using a lightweight mapper when needed ( <a href="https:&#x2F;&#x2F;github.com&#x2F;StackExchange&#x2F;Dapper" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;StackExchange&#x2F;Dapper</a> which the stackoverflow people created )<p>I gotta say, I kind of like it<p>One of the problems of many stacks is that the frameworks wrap general purpose languages over SQL, which, is not really a good idea, SQL is a vastly more capable language for dealing with relational data and layers built over the top often dumb down the database.<p>The REAL problem SQL wrappers need to solve is that most languages don&#x27;t have a good interface with SQL.  So most often SQL is handled in strings and manipulated with string manipulation and there is no type safe way transitioning data from the DB to a general purpose language.<p>Microsoft at one stage had Linq to SQL which was quite good..... but they killed it :)