Based on our record, ProxySQL should be more popular than Falcor. It has been mentiond 10 times since March 2021. 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.
Interesting the article jumps straight from REST to GraphQL and forgets Falcor[0] - Netflix's alternative vision for federated services. For a while it looked like it might be a contender to GraphQL but it never really seemed to take off despite being simpler to adopt. [0] https://netflix.github.io/falcor/. - Source: Hacker News / 9 months ago
- obviously netflix with falcor, EVCache and hundreds of other projects. Source: about 2 years ago
I pushed for Falcor over GraphQL in 2016. I still think Falcor was a more elegant core idea, but the implementation, tooling, and community never materialized like it did with GraphQL, and now Falcor is relatively niche and obscure. Netflix wasn't willing or able to promote it like Facebook did with GraphQL. That was beginning to be apparent in 2016, but I liked the concept too much. Source: almost 3 years ago
Netflix has two amazing aspects I think. One is obviously the movie infrastructure and the other the way they do data and state management. I would read up on https://netflix.github.io/falcor to get an idea what is involved here.to be honest I dont get the point of rebuilding the visual aspects of their web app, that part is trivial and also completely useless without the parts that matter. Source: about 3 years ago
Another option could be ProxySQL, where you can cache queries on the ProxySQL server. Source: about 1 year ago
Also, if you're not using it yet, I can recommend looking at ProxySQL to do your read-write/read-only failover controls. Source: over 1 year ago
What are the recommendations here? I took a look into ProxySQL and it looks like since v2, it can do frontend and backend SSL connections. I have it locally working on a docker setup. Source: over 1 year ago
DB: Split you write-read operations. You may scale read as needed. Write operations can be slow if you have too many indices, so make sure to use only the ones you really need. Your DBMS may have some configuration to optimise, for example in MySQL if you do NOT need ACID compliance you can set innodb_flush_log_at_trx_commit = 2 to achieve better write speed. For MySQL you should also look into https://proxysql.com/. Source: over 1 year ago
A Layer-7 Database Load Balancer is optional here. An L7-DBLB can be used for various use cases (eg: ProxySQL). One or more database instances handle queries from the web server. A Client-side DB query/connection load balancing can also be used instead of an L7-DBLB according to the use case of the application. - Source: dev.to / almost 2 years ago
GraphQL - GraphQL is a data query language and runtime to request and deliver data to mobile and web apps.
Gonarch Tech - MySQL High Availability as a service
OData - OData, short for Open Data Protocol, is an open protocol to allow the creation and consumption of queryable and interoperable RESTful APIs in a simple and standard way.
PostgREST - Automatic REST API for Any Postgres Database
LoopBack.io - A highly extensible Node.js and TypeScript framework for building APIs and microservices.
MariaDB MaxScale - We are the company behind #MariaDB, the fastest growing #opensource #database. Download MariaDB at https://t.co/DtYwuH0FOl.