Hot answers tagged

5

The problem with the last option is that I would still need somewhere to store queue metadata information like creation date. Other than you may store other fields (like timestamp) in Metadata database, Metadata service should scale out well for reads and be highly available as every PUT and GET call for a message results in a call to the Metadata service. ...


2

The first things first. There are two completely different types of "API"s people call RESTful. First, the original meaning as described by Roy Fielding essentially describes how you create a web application. A RESTful API is basically a web-application for machines, but works exactly as a web-application for humans. That is, it starts with a ...


2

As short outages (long enough to restart a VM) are acceptable, you don't need the immediate failover capability of an active/standby configuration. That makes the main concern that you don't get a corruption of the database storage. You have partially tacked that by having redundant storage with a main database and a backup database. What still can go wrong ...


Only top voted, non community-wiki answers of a minimum length are eligible