Answer the question
In order to leave comments, you need to log in
REST or Json-RPC for a big project?
It is necessary to write applications in which communication between the front-end and the back-end will be built using the API.
Technology stack: frontend - python, backend - golang. The frontend does not store state.
In fact - you need a CRUD model. How relevant is it to use json-rpc now?
In this case, you need to take into account that there will be several hundred methods or urls.
Answer the question
In order to leave comments, you need to log in
At its core, CRUD is resource oriented.
What you describe pushes towards REST. Dopilit you it to the absolute RESTful is another matter.
If out of several hundred methods there will be >50% to implement CRUD . Then definitely REST.
Argument from linkedin:
https://www.linkedin.com/pulse/rest-vs-rpc-soa-sho...
json rpc is when all post requests.
rest is the style of architecture. It is not about urls and not about http. Simply on http it lays down very well.
Well, that is, you can do everything adhering to the principles of REST. The main thing is not to confuse http and rest and do not limit yourself to the idea that resources are a display of plates in the database.
What's the difference? You will have some kind of router anyway.
REST is preferable, in my opinion, as it eats less resources, it is easier to debug, it is easier to use. Well, of course, drive the data in json.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question