Nope. Does not make sense for application with static data that is rarely changed. SSEs require HTTP/2 and exclude most applications. Makes more sense in case of realtime messaging where data is created constantly in the backend and a frontend would like to get that immediately.
For backend-to-backend communication in that case, gRPC is another option.
Nope. Does not make sense for application with static data that is rarely changed. SSEs require HTTP/2 and exclude most applications. Makes more sense in case of realtime messaging where data is created constantly in the backend and a frontend would like to get that immediately.
For backend-to-backend communication in that case, gRPC is another option.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Nope. Does not make sense for application with static data that is rarely changed. SSEs require HTTP/2 and exclude most applications. Makes more sense in case of realtime messaging where data is created constantly in the backend and a frontend would like to get that immediately.
For backend-to-backend communication in that case, gRPC is another option.