Back4App
Firebase
Heroku
CouchBase
Parse
Kuzzle
Kumulos
AWS Amplify
Apache Thrift
Docker Hub
Apache ZooKeeper
Eureka
Avro
SkyDNS
gRPC
runc
Back4App supports developers and companies to accelerate backend development, improve development productivity, reduce time to market, and scale applications without managing infrastructure.
Back4App
Apache ThriftBack4App is recommended for startups, indie developers, and enterprises that require a reliable and cost-effective backend service to rapidly develop and deploy applications. It is ideal for those who prefer not to manage their own servers or infrastructure and for projects that need quick scalability and real-time data management, such as social apps, mobile applications, and IoT solutions.
Based on our record, Apache Thrift seems to be a lot more popular than Back4App. While we know about 13 links to Apache Thrift, we've tracked only 1 mention of Back4App. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
I'm using back4app.com which is a cloud service for parse server, you can fire cloud code using node. Recently they introduce containers, but I didn't use it. Source: over 3 years ago
I once read a paper about Apache/Meta Thrift [1,2]. It allows you to define data types/interfaces in a definition file and generate code for many programming languages. It was specifically designed for RPCs and microservices. [1]: https://thrift.apache.org/. - Source: Hacker News / almost 2 years ago
While gRPC and Apache Thrift have served the microservice architecture well, CloudWeGo's advanced features and performance metrics set it apart as a promising open source solution for the future. - Source: dev.to / over 2 years ago
Services in general communicate via Thrift (and in some cases HTTP). Source: over 3 years ago
Protocol Buffers is the most popular one, but there are many others such as Apache Thrift and my own Typical. Source: over 3 years ago
RPC is not strictly OO, but you can think of RPC calls like method calls. In general it will reflect your interface design and doesn't have to be top-down, although a good project usually will look that way. A good contrast to REST where you use POST/PUT/GET/DELETE pattern on resources where as a procedure call could be a lot more flexible and potentially lighter weight. Think of it like defining methods in code... Source: over 3 years ago
Firebase - Firebase is a cloud service designed to power real-time, collaborative applications for mobile and web.
Docker Hub - Docker Hub is a cloud-based registry service
Heroku - Agile deployment platform for Ruby, Node.js, Clojure, Java, Python, and Scala. Setup takes only minutes and deploys are instant through git. Leave tedious server maintenance to Heroku and focus on your code.
Apache ZooKeeper - Apache ZooKeeper is an effort to develop and maintain an open-source server which enables highly reliable distributed coordination.
CouchBase - Document-Oriented NoSQL Database
Eureka - Eureka is a contact center and enterprise performance through speech analytics that immediately reveals insights from automated analysis of communications including calls, chat, email, texts, social media, surveys and more.