What is Art Blocks' tech stack and what are the key infrastructure components?

I wrote Art Blocks as someone that studied on the Codecademy website for a few months. I wrote the infrastructure as a node server, and the frontend was React, JavaScript React. Obviously, we have a smart contract. 

The idea is that on the frontend, you are sending a smart contract transaction to the smart contract, and then on the backend, the infrastructure is sensing for the new mint. The moment that it senses the new mint—and it allows for three confirmations because we've had block reorgs that present people the wrong output, which is really disappointing when the output you get you like better than the one that you actually end up getting— the infrastructure renders the mint, because most places need a thumbnail or an image. 

One of the most beautiful things that happened last year was when OpenSea, when you opened the Art Blocks mint, instead of it just grabbing the image from S3, it started playing the live algorithm in a little box. So that was really special. But we also need to generate a rendering because a lot of platforms need a rendered image to be able to display, so we have our API that returns the information necessary to recreate the image. It returns a lot of the metadata, a lot of which is not on-chain because ultimately, what's on-chain is the art itself. 

I definitely went through a transition where I handed off engineering entirely to a very special and brilliant group of engineers that have really taken my science project and turned it into a very robust engineering masterpiece, in my opinion. As that's happened, I've taken a step back, so I don't know exactly how it all works anymore, which is really sad, but also, my bandwidth just doesn't permit that level of diving in.