The Openfount Queued Server presents an intriguing approach to web architecture. Although it took some time to grasp its structure, this investment in understanding proved to be worthwhile.
At its core, this technology creates a buffer of processing queues that sit between a web client and a backend server. These queues utilize the S3 and SQS services. The client does not communicate directly with the server; instead, it employs APIs from the Queued Server toolkit to send messages into a queue for the server to handle. Once the server processes these messages, it returns values via another queue from which the client retrieves and displays the results. It seems likely that the client incorporates some type of event loop or notification system, facilitating the creation of dynamic, Ajax-styled applications.
Since the server actively polls the queue for messages, it does not require any public-facing interface—no domain name, no IP address, and thus, no exposure to common attack vectors. The server could even operate behind a cable modem with a dynamic IP address, remaining undetected, as it connects to the internet through standard HTTP requests over port 80. In this configuration, the server does not accept incoming calls directly; it selectively pulls in requests, maintaining control over which ones it processes.
Moreover, this design isolates and protects both clients and servers from one another, meaning the client does not need to know the server’s domain name or IP address.
Building scalable web applications with this method should be straightforward. When the server is momentarily busy, the queues simply accumulate. Since the server manages request processing entirely, it is unlikely to be overwhelmed by traffic. If demand exceeds the capacity of a single server, scaling up by adding additional servers is easy. In either scenario, S3 and/or SQS provide the necessary elasticity to accommodate fluctuating traffic patterns.
The pricing structure is tiered based on the number of unique users per month, starting at just $3 for up to 100 users and reaching $83 for a billion users. It remains unclear whether this includes fees for S3 and SQS.
For further insights, you might find this other blog post here to be engaging. Additionally, for authoritative information on this subject, check out this source. Lastly, those interested in insights about the first week of working at an Amazon warehouse can refer to this excellent resource.
— Alex;
Alex Smith is the Chief Evangelist for AWS. He began this blog in 2004 and has consistently contributed since.
SEO Metadata
Leave a Reply