July/August 2018 issue of acmqueue The July/August issue of acmqueue is out now
Subscribers and ACM Professional members login here

Web Services

  Download PDF version of this article PDF

Error 526 Ray ID: 46d020832dfb214a • 2018-10-21 01:59:49 UTC

Invalid SSL certificate








What happened?

The origin web server does not have a valid SSL certificate.

What can I do?

If you're a visitor of this website:

Please try again in a few minutes.

If you're the owner of this website:

The SSL certificate presented by the server did not pass validation. This could indicate an expired SSL certificate or a certificate that does not include the requested domain name. Please contact your hosting provider to ensure that an up-to-date and valid SSL certificate issued by a Certificate Authority is configured for this domain name on the origin server. Additional troubleshooting information here.


Originally published in Queue vol. 6, no. 6
see this item in the ACM Digital Library



Silvia Esparrachiari, Tanya Reilly, Ashleigh Rentz - Tracking and Controlling Microservice Dependencies
Dependency management is a crucial part of system and software design.

Diptanu Gon Choudhury, Timothy Perrett - Designing Cluster Schedulers for Internet-Scale Services
Embracing failures for improving availability

Štěpán Davidovič, Betsy Beyer - Canary Analysis Service
Automated canarying quickens development, improves production safety, and helps prevent outages.

Benjamin Treynor Sloss, Mike Dahlin, Vivek Rau, Betsy Beyer - The Calculus of Service Availability
You're only as available as the sum of your dependencies.


(newest first)

mawahib | Tue, 10 Sep 2013 09:49:37 UTC


can help me to understand what eventual consistency means

Eventual consistency. This is a specific form of weak consistency; the storage system guarantees that if no new updates are made to the object, eventually all accesses will return the last updated value. If no failures occur, the maximum size of the inconsistency window can be determined based on factors such as communication delays, the load on the system, and the number of replicas involved in the replication scheme. The most popular system that implements eventual consistency is DNS (Domain Name System). Updates to a name are distributed according to a configured pattern and in combination with time-controlled caches; eventually, all clients will see the update.


Maik G. Seewald | Fri, 19 Dec 2008 07:47:39 UTC

This is a remakable statement about a paradigm change. The upcoming new world of the clouds will lead in this direction and most uf us must follow. Anyway, we need to consider thoroughly in which areas these BASE and CAP approaches are applicable (and where definitely not).

Jeroen Wyseur | Fri, 05 Dec 2008 08:26:21 UTC

This article makes me think further about where my data lives and how I can keep it consistent. It also gives a good introduction in how a clustered database provides availability and consistency and what the tradeoffs are to this.

I would think about any place where the data lives, what could also be a cache or at the client side instead of only the server side. All that data will need to become consistent at a certain moment in time. This does not mean that it is not ok to have out of date data.

Leave this field empty

Post a Comment:

© 2018 ACM, Inc. All Rights Reserved.