Posts Tagged Under: REST

Offloading To Workers – A Hands-On Example

Services offload their computationally expensive tasks into workers. Think of software that converts video from its original format to a web standard. This kind of job can be considered long-running, even for state-of-the-art hardware. The web app can’t convert the video, it doesn’t have access to the software and, even if it did, we’d have little control over what ends up on our servers. The service used by the app could convert the video, but it would take valuable processing time shifting though millions of requests.

Read More

REST Best Practices: Managing Concurrent Updates

In a previous article, we described how to choose a HTTP method when implementing operations that affect resources. Today, we are going to explain how to implement services that manage concurrent operations on a resource and how clients should use such services.

The Problem

Sometimes, Apps must handle concurrent updates on a resource. Just imagine an application that acts like a Wiki, where users read, write, and edit articles.

Read More

REST Best Practices: Choosing HTTP Methods

We do a lot of REST in the Pineapple team. We love REST. Why? There are many reasons:

  • It is standard, so that creating services always follows a pattern
  • Developing clients is super easy, in all programming languages
  • Programmers can easily understand it
  • Testing (of all types) can be easily automated
  • Because it relies on HTTP, it’s highly scalable infrastructure wise
  • We can choose the preferred data format for sending and receiving information – usually JSON 🙂

Read More