Thread by @EllieOnSoftware

I've spent a few hours spiking a first AWS microservice to extract from our Rails monolith. I had thought to use the node.js runtime, because "JS is a lingua franca among web devs" (maintainability), and given I know JS, it should be easy to get going, right? WRONG

Hoo boy. node.js and async-first JS is nothing like anything I've encountered in the browser. I spent most of the time slamming my head against learning the ins and outs of async/await and how to cross seams between promise rejection and traditional errors

Then hit another wall when I tried to integrate the client library for a third-party platform we integrate with

I'm going to make a run at a Ruby version the next time I sit down with it. At least I have my test cases defined & can port them over to RSpec

Or heck, as long as I am visiting foreign platforms, maybe I should try out a golang version