API Design Best Practices for long-running Operations: GraphQL vs REST. .css-ze3n0k{outline:0;margin-top:2rem;line-height:1.2;font-weight:var(--chakra-fontWeights-bold);font-size:1-1.875rem;letter-spacing:-.025em; margin-bottom:var (-- chakra-space-4);}.css-a9v878>*:not(style)~*: not(style);.css-3wye89{width:100%;display:flex;-webkit-box-align:center;
Table of contents
What actually is a long-running operation? .css-zs7ok4{color:var(--chakra-colors-teal-500);font-weight:var(--chakra-fontWeights-normal);outline:none;opacity:0;margin-left:0.375rem;}.css-zs7ok4:focus,.css-zs7ok4[data-focus]{opacity:1;box-shadow:var(--chakra-shadows-outline);}[role=group]:hover .css-zs7ok4,[role=group][data-hover] .css-zs7ok4,[data-group]:hover .css-zs7ok4,[data-group][data-hover] .css-zs7ok4,.group:hover .css-zs7ok4,.group[data-hover] .css-zs7ok4{opacity:1;} #Designing a synchronous REST API for long-running operations #Designing an asynchronous REST API for long-running operations #Designing an asynchronous GraphQL API for long-running operations #Comparing REST and GraphQL for long-running operations #Conclusion #1 Comment
Sort: