Last modified by Ashterix on 2024/05/20 12:55
From version 1.1
edited by Ashterix
on 2024/05/12 10:50
Change comment: There is no comment for this version
To version 2.1
edited by Ashterix
on 2024/05/20 12:55
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -2,6 +2,7 @@
2 2  (((
3 3  (% class="container" %)
4 4  (((
5 +[[image:rpc.png||alt="rpc_vs_rest_vs_grafql" data-xwiki-image-style-alignment="end" height="281px" width="500px"]]
5 5  = My View on Modern APIs =
6 6  
7 7  I will try to express my opinion here and explain why Json-RPC is a better choice for building APIs.
... ... @@ -86,4 +86,3 @@
86 86  Considering the advantages outlined above, Json-RPC is an ideal candidate for selection as the main API architecture in a wide range of projects. This technology not only improves the interaction between different parts of IT infrastructure but also facilitates rapid adaptation to new business demands and technological conditions.
87 87  
88 88  Choosing Json-RPC can significantly optimize development and implementation processes, providing the resilience and flexibility that are key to modern business ecosystems.
89 -