Ю
Аж ливнул ради интереса
Size: a a a
2020 September 23
N
кнопак многа
NZ
На новом не веб апи)
autorest не пробовали?
VL
autorest не пробовали?
No
2020 September 24
A
Hey guys, I have question.
Should I use gRPC or RESTin my project?
And is it better to know gRPC or REST?
I want your opinions cause I'm still new to this😁
Should I use gRPC or RESTin my project?
And is it better to know gRPC or REST?
I want your opinions cause I'm still new to this😁
AK
Hey guys, I have question.
Should I use gRPC or RESTin my project?
And is it better to know gRPC or REST?
I want your opinions cause I'm still new to this😁
Should I use gRPC or RESTin my project?
And is it better to know gRPC or REST?
I want your opinions cause I'm still new to this😁
REST
A
Why
Ш
Why
Because
OZ
Hey guys, I have question.
Should I use gRPC or RESTin my project?
And is it better to know gRPC or REST?
I want your opinions cause I'm still new to this😁
Should I use gRPC or RESTin my project?
And is it better to know gRPC or REST?
I want your opinions cause I'm still new to this😁
It depends. gRPC's biggest pros: common contract between caller and callee defined in platform-independent language, http v2 under the hood and the amount of data transferred per call. Limitation is that gRPC can't be used in modern browsers (this is why gRPC-web was developed).
1. If I wanted to set up RPC communication between 2 back end services (imagine it as a part of SOA) I would use gRPC.
2. For web API I would use graphql unless I hit an edge case where I would be forced to use HTTP API.
P.S. if getting a first job is your primary goal I suggest studying HTTP API as it's still widely used and most likely your first job will require knowledge of this thing
1. If I wanted to set up RPC communication between 2 back end services (imagine it as a part of SOA) I would use gRPC.
2. For web API I would use graphql unless I hit an edge case where I would be forced to use HTTP API.
P.S. if getting a first job is your primary goal I suggest studying HTTP API as it's still widely used and most likely your first job will require knowledge of this thing
V
It depends. gRPC's biggest pros: common contract between caller and callee defined in platform-independent language, http v2 under the hood and the amount of data transferred per call. Limitation is that gRPC can't be used in modern browsers (this is why gRPC-web was developed).
1. If I wanted to set up RPC communication between 2 back end services (imagine it as a part of SOA) I would use gRPC.
2. For web API I would use graphql unless I hit an edge case where I would be forced to use HTTP API.
P.S. if getting a first job is your primary goal I suggest studying HTTP API as it's still widely used and most likely your first job will require knowledge of this thing
1. If I wanted to set up RPC communication between 2 back end services (imagine it as a part of SOA) I would use gRPC.
2. For web API I would use graphql unless I hit an edge case where I would be forced to use HTTP API.
P.S. if getting a first job is your primary goal I suggest studying HTTP API as it's still widely used and most likely your first job will require knowledge of this thing
Main thing in most of projects today that use REST over HTTP - they actually reinvent RPC over HTTP, lol
V
I haven't seen pure REST as in books in any solution I was working on
V
Because plain REST is not satisfying any complicated enough business model
V
Hey guys, I have question.
Should I use gRPC or RESTin my project?
And is it better to know gRPC or REST?
I want your opinions cause I'm still new to this😁
Should I use gRPC or RESTin my project?
And is it better to know gRPC or REST?
I want your opinions cause I'm still new to this😁
So to sum up, you should first learn REST principles enough to see if they fit to your goals and if not - try GraphQL or gRPC
A
Thanks, mate, appreciate it
V
наверно симпл будет слишком симпл, попробую автофак, что-ли
Симпл достаточно не симпл
V
Симпл достаточно не симпл
Главное нинжект не юзать🌚
V
Главное нинжект не юзать🌚
+
OZ
I haven't seen pure REST as in books in any solution I was working on
😊 именно по той же причине я и не употреблял этой аббревиатуры у себя в ответе
OM
Блок try catch даёт какой то импакт на производительности?
IP
😊 именно по той же причине я и не употреблял этой аббревиатуры у себя в ответе
Тоже и к репозиторию можно отнести)