CEO from Baqend here.<p>This announcement will have a huge impact for the mobile dev community that relies on Backend-as-a-Service systems. I personally think that Facebook had several reasons to shut down Parse:<p>1) The technology stack was really fragmented and often rewritten in large parts. I still have this statistic in mind how their 200 Rails API servers were only able to serve 15 requests&#x2F;s each [1]. If you look at the database technology inside Facebook, there is much superior infrastructure that was never really integrated into Parse (Haystack@OSDI&#x27;10, Tao@ATC&#x27;13, F4@OSDI&#x27;14, Extended Apache Giraph@VLDB&#x27;15, RocksDB, etc.)<p>2) Parse did not have a core competitive advantage: it was just the first company to whole-heartedly pick up the BaaS-paradigm with sufficient man power and a good understanding of developers&#x27; needs. The technology itself was not particularly innovative in any way, just (mostly) solid engineering. However, there remained really basic limitations that were never addressed [2]. For instance the only (!) way to safely handle concurrency control was through counter data types.<p>3) The model of Parse promotes independent apps and websites outside the Facebook universe.<p>4) The pricing in increments of guaranteed 30 requests&#x2F;s was okay for simple apps but absolutely useless for anything beyond that. In particular for websites which as of 2016 do an average of 100 requests per page load [2] a single user can leave a Parse app rate-limited or down.<p>The main asset of Parse were their great client SDKs and well-written documentation.<p>This is why we made a plan: we will fork the Parse SDKs to offer seamless continuation of apps relying on them, including Push and the other features dropped in the open-source Parse Server. We opted for this approach as the Parse Server implementation on Github looks really brittle and the convoluted Parse REST API is really not an option. By doing this we hope to provide a scalable and long-term solution for developers looking to continue their Parse-based apps.<p>Baqend [2] is a pre-seed startup founded out of the database research group at the University of Hamburg (Germany). Our product launching into production within the next months uses a new approach to consistent web-caching reducing latency in common web workloads by up to an order of magnitude [5]. It is due to this background that we very eager to not only provide great usability (which Parse also did) but also acknowledge the need for complex data processing: low latency access, partial updates, continuous queries and ACID transactions.<p>We&#x27;ll post a detailed plan on our blog, soon.<p>[1] <a href="http:&#x2F;&#x2F;blog.parse.com&#x2F;learn&#x2F;how-we-moved-our-api-from-ruby-to-go-and-saved-our-sanity&#x2F;" rel="nofollow">http:&#x2F;&#x2F;blog.parse.com&#x2F;learn&#x2F;how-we-moved-our-api-from-ruby-t...</a>
[2] <a href="http:&#x2F;&#x2F;profi.co&#x2F;all-the-limits-of-parse&#x2F;" rel="nofollow">http:&#x2F;&#x2F;profi.co&#x2F;all-the-limits-of-parse&#x2F;</a>
[3] <a href="http:&#x2F;&#x2F;httparchive.org&#x2F;trends.php&#x2F;" rel="nofollow">http:&#x2F;&#x2F;httparchive.org&#x2F;trends.php&#x2F;</a>
[4] <a href="http:&#x2F;&#x2F;www.baqend.com&#x2F;" rel="nofollow">http:&#x2F;&#x2F;www.baqend.com&#x2F;</a>
[5] <a href="http:&#x2F;&#x2F;www.btw-2015.de&#x2F;res&#x2F;proceedings&#x2F;Hauptband&#x2F;Wiss&#x2F;Gessert-The_Cache_Sketch-165.pdf" rel="nofollow">http:&#x2F;&#x2F;www.btw-2015.de&#x2F;res&#x2F;proceedings&#x2F;Hauptband&#x2F;Wiss&#x2F;Gesser...</a>