4 ms·

So it works? And there are no errors?

• retrocryptid 5y ago
  there are plenty of errors. it works only intermittently, produces megabytes of randomly generated files as a side effect and spurious messages to various internal pub/sub topics. users know to send a request and wait 30 seconds. if it doesn't respond, just resubmit the request. it also has no build system or tests, just a script that copies the source to a build directory, zips it up and uses an example SAM template that creates quite a few unused resources, but as a side effect creating a useful lambda. the lambda is behind an api gateway resource/method so a payload is sent to the lambda if the request path matches what's in the resource path part of the api. the lambda itself is an express app with a single route defined (which is the same as the api gateway resource path) - so the api gateway routes to the lambda if the path in matches the resource. then the express app looks at the path and dispatches based on the path (even though the only way you could have called this lambda was for the path to already match the path specified in the express app.) because there's no build system, they didn't think to scrape dev dependencies out of the build directory, so we wind up uploading babel and a few other packages to the deploy environment. we're inconsistant in whether we use SNS vs. SQS. and we frequently drop requests if we get a sudden spike in traffic because SNS is not a queue and sometimes it takes so long to scale up messages time out of the SNS topic. but it "works" for some definition of the word.