Trust em or not … had that happen to someone else using Cursor a few weeks back. I ran a prompt for refactoring a function and all of a sudden it started dumping someone else’s directory structure and file contents into my text file. Like hundreds of files. Not exactly sure what happened but I immediately uninstalled Cursor.
Yep. Massdriver [0] is built on elixir and golang.
All user facing APIs and cloud provisioning state is written in elixir and runs on pretty much just fumes. Cloud systems interaction is written in golang because cloud stuff.
Email is in profile if you’d like to chat. Always happy to talk elixir and golang
I wrote the lambda piece, you could say re-arch saved us the money (although we could only re-arch cheaply because we already had other massive scale serverful systems in place), but I don’t believe I could have made it as efficient and dependency free in any other language.
i had been developing in ruby for over a decade and about 5 years of Node exp at the time.
im not a language enthusiast and mostly write in go today.
Author of the “Lambda” piece [0], all of the cost savings I discussed came from API Gateway alone. The lambdas were negligible.
That being said, I don’t think we could have processed the traffic more efficiently in another language.
We were processing 12M requests per hour. You could run the entire thing on 2 vCPU we “over provisioned the crap out of it” by running it on 4 pods w 2 vCPU as the upper request limit.
> Our service didn’t quite grow exponentially in use, but it did hockey stick. It went from free, to a few hundred bucks, to around $12,000 just for API Gateway. No Kinesis. No Lambda. Just API Gateway.
> A good part of this entire system still runs in Lambda, although it will be moving into Elixir over time to make it easier to reason about and develop on locally.
> What everyone should do is think about where your service is going, and can you afford those costs when you get there. If you don’t have a team of ops people and you aren’t familiar with serverful stuff, spending $30k/mo on HTTP requests might be cheaper than an ops team.
I am very curious about the future of Nomad. It definitely has its place for some orgs and was exciting to see an alternative to k8s gaining traction.
I think this license change will hamper adoption and contribution when teams compare a foundation supported k8s vs a source available Nomad. I haven’t heard of anyone taking this on, but I’d love to keep my eyes on it if/when it happens.
Disclaimer: early supporter of opentf, cofounder of massdriver