ctcliff

I maintain a small open source library for managing payments websites that uses this architecture [1]. My Lambda costs have been about $0.04 per transaction.

Also you can provision AWS from the browser using a CloudFormation template and a Launch Stack URL [2].

[1]: https://github.com/christophercliff/flatmarket. [2]: https://github.com/christophercliff/flatmarket#automated-dep...

An old stock art CD-ROM by Redouté.

I developed a static site generator for e-commerce called Flatmarket: https://github.com/christophercliff/flatmarket

It lacks some of the features you'd get with a dedicated backend service but it's truly static and costs about $0.004/transaction on AWS Lambda (not including Stripe's take).

I haven't, but even at this size the rendering is quite a bit slower than the calculation. For example, the delay on reload is almost entirely from rendering the shortest path tree.

The geographic rendering APIs tend to be incompatible with the graphing algorithms and data structures. It's better to optimize your data on the server for algorithmic simplicity and convert to a render-friendly format at render time.

Also, immutability is great when you're juggling 1000s of lon/lat arrays.

Yeah, that was an unpleasant surprise when I started plugging in the street map data :D

I'm experimenting with other algorithms and will post some (hopefully) more interesting results soon.

This setup assumes manual order fulfillment. If someone manipulates a charge, don't deliver the goods.

If you're doing 100s of transactions per day or automating fulfillment, it would be more appropriate to invest in a full-featured back end.

Loads of examples at http://highlandjs.org/.

I wrote an npm module to automate this workflow. You can read about it at http://caisson.co/.

Simplifies the process to a couple commands:

  $ caisson init yoursite.com
  $ caisson push

It's just a convention for writing jQuery chains. The code is easier to debug because each method is kept on a separate line.

Of course this is trivial if there's only one method in the chain...