Cloud Hosting

In what may be the strangest retrocomputing project weve seen lately, you can now access a virtual 6502 via Amazons Lambda computing service. We dont mean theres a web page with a simulated CPU on it. Thats old hat. This is a web service that takes a block of memory, executes 6502 code that it finds in it, and then returns a block of memory after a BRK opcode or a time out.

You format your request as a JSON-formatted POST request, so anything that can do an HTTP post can probably access it. If you arent feeling like writing your own client, the main page has a form you can fill out with some sample values. Just be aware that the memory going in and out is base 64 encoded, so you arent going to see instantly gratifying results.

You may not be familiar with Amazon Lambda. It is the logical extension of the Amazon cloud services. Time was that you paid to have a server in a data center. The original Amazon cloud services let you spin up a virtual server that could come into existence when needed. You could also duplicate them, shut them down, and so on. However, Lambda is even one step further. You dont have a server. You just have a service. When someone makes a request, the Amazon servers handle it. They also handle plenty of other services for other people.

Theres some amount of free service, but eventually, they start charging you for every 100 ms of execution you use. We dont know how long the average 6502 program runs.

Is it practical? We cant think of why, but weve never let that stop us from liking something before. Just to test it, we put the example code into an online base64 decoder and wound up with this:

Then we went over to an online 6502 disassembler and got:

We then ran the 6502cloud CPU and decoded the resulting memory output to (with a bunch of trailing zeros omitted):

So for the example, at least, it seems to work.

Weve covered giant 6502s and small 6502 systems. We have even seen that 6502 code lives inside Linux. But this is the first time we can remember seeing a disembodied CPU accessible by remote access in the cloud.

See the article here:
6502 Retrocomputing Goes to the Cloud - Hackaday