POSTとPUTの使い分け : アジャイル株式会社
RESTful API設計におけるHTTPステータスコードの指針 - Qiita
REST and microservices - breaking down the monolith step by asynchronous step | Red Hat Developer
A few days ago I had a rant about the misuse and misunderstanding of REST (typically HTTP) for microservices. To summarize, a few people/groups have been suggesting that you cannot do asynchronous interactions with HTTP, and that as a result of using HTTP you cannot break down a monolithic application into more agile microservices. The fact that most people refer to REST when they really mean HTTP
Rubyist Magazine - スはスペックのス 【第 1 回】 RSpec の概要と、RSpec on Rails (モデル編)
JWTUMOIM: Act 3
I'd say I've looked at about a hundred different web service designs. I've tried to design good web services. I want to distinguish between good web services and bad ones, and figure out what is the relationship between the constraints of REST and subjectively determined web service quality. I figured out about two-thirds of the answer while I was writing RESTful Web services. What I'm about to sh
リソースの一部更新におけるURL設計 - Qiita
REST, where’s my state?
HTTP, the Hypertext Transfer Protocol, has been designed under the constraints of the REST architectural style. One of the well-known constraints of this REpresentational State Transfer style is that communication must be stateless. Why was this particular constraint introduced? And who is in charge then of maintaining state, since it is clearly necessary for many Web applications? This post expl
The S in REST
18 August 2014 REST is a vast improvement over complex things like SOAP and CORBA, but I think we still have a way to go before we’ve reached simple. REST is an acronym for REpresentational State Transfer, and I think the “state” part of that acronym gives rise to a lot of incidental complexity as systems grow. You can think of state as a combination of value and time, and in the RESTful case, the
HerokuのAPIデザイン
RESTistential Crisis over Hypermedia APIs
Scaling Challenges: Productivity, Cost Efficiency, and Microservice Management The main objective of this article is to delve into the technical complexities and strategic adjustments undertaken by Trainline. By examining challenges such as managing peak transaction volumes and orchestrating microservice architectures, we aim to uncover the valuable lessons learned and insights gained from Trainli
API Exchange
Please note: GSMA’s Federated Discovery Service has ended – for more information please contact the team at [email protected]. The API Exchange enables operators to federate between their individual APIs to deliver cross-operator reach. API Exchange: Global API Federation capability The API Exchange: Reach and Flexibility The API Exchange serves to bridge the gap between application providers’ nee
REST Commander: Scalable Web Server Management and Monitoring
REST Commander: Scalable Web Server Management and Monitoring In the era of cloud and XaaS (everything as a service), REST/SOAP-based web services have become ubiquitous within eBay’s platform. We dynamically monitor and manage a large and rapidly growing number of web servers deployed on our infrastructure and systems. However, existing tools present major challenges when making REST/SOAP calls w
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Is REST DELETE really idempotent?
What is the appropriate HTTP response code to a successful DELETE request?
DELETE is for Saying Goodbye
What Is Idempotent in REST?
RESTful design: when to use sub-resources?
REST - supporting multiple possible identifiers
Open Mobile Alliance - Specifications
GitHub - axsh/sinatra-browse: Parameter declaration framework and browsable API for Sinatra
