Their solution is graphql, but I believe that the backend should have data for each component ready.
Example social network.
/api/pagedata/FrontPage
returns a big ass query result, all posts with comments, comment count and reactions, all the data you would ever want in your front page.
/api/pagedata/UserProfilePage
returns all the relevant data regarding the user's profile page.
Yes, if you change or extend a certain page, you will have to change the backend query. If you have 2 different teams for frontend and backend that's not straightforward, so there should be something where the frontend team writes the detailed expected json response and the backend team transforms that into queries.
Or, let's be real, the queries get generated.
One could even imagine a middleware that translates expected json to graphql queries.
Why not directly graphql? Because it's a major pain in the ass, because of relay. Graphql is Facebook. And instead of having the simple structure you can easily query, they added this stupid node relay structure which makes everything overly complicated.
I could imagine a Go backend or Rust where you have a comment with the expected JSON, and you type go generate and boom generated queries with search and pagination.
Now it's also 3 videos in 90 days you have to publish in order to be eligible for monetization.
So you can't have passive income at YouTube, you have to create a new video each month.
3000 watched hours or 3 million shorts views lol.
They want only the cream.
But dethroning the king would need an ad delivery solution, which in turn requires an affordable payment solution.
And you would need to keep it civil, because now, if you're in the EU are liable for what people upload.
And then, thanks to the DSA, you have to monitor "wrong speak".
How is anyone supposed to bring up a competitor with those blockers?
I'm not talking about auctions. I'm talking about regular servers.
And I get those facts from ACTUALLY FUCKING TRYING TO CONFIGURE MORR THAN 3 HDDS on those machines.
You go ahead and try it before talking out your ass and downvoting.
Example social network.
returns a big ass query result, all posts with comments, comment count and reactions, all the data you would ever want in your front page.
returns all the relevant data regarding the user's profile page.
Yes, if you change or extend a certain page, you will have to change the backend query. If you have 2 different teams for frontend and backend that's not straightforward, so there should be something where the frontend team writes the detailed expected json response and the backend team transforms that into queries. Or, let's be real, the queries get generated. One could even imagine a middleware that translates expected json to graphql queries.
Why not directly graphql? Because it's a major pain in the ass, because of relay. Graphql is Facebook. And instead of having the simple structure you can easily query, they added this stupid node relay structure which makes everything overly complicated.
I could imagine a Go backend or Rust where you have a comment with the expected JSON, and you type go generate and boom generated queries with search and pagination.