I enjoy this article and it hurt a little to read. Tha part about RabbitMQ especially hurt. This has been my life for a while. Give me our monolithic software any day.

[–] bouncing@partizle.com 0 points 2 years ago (1 children)

You do need a message queue sometimes. Though I've often found that just inserting into a table works well enough if you plan your indexes right.

[–] GoldenBooger@partizle.com 0 points 2 years ago (1 children)

My view on it is that companies build cargo ships when most just need a normal boat. For the particular orchestration I am thinking of, it scales to massive use with billions of transactions. The problem is, the idle infrastructure is so big and the bulk of deployments don't need that potential. I agree with you. For much of what I have done for myself I have learned to love sqlite3. I love the simplicity of one process and one file.

[–] bouncing@partizle.com 1 points 2 years ago

The projects I'm working with are big enough to rule out one process/one file, but I agree. Part of all of this is why things like Heroku, Google App Engine, and fly.io all appeal to me (especially the early Guido-era App Engine). They had all this infrastructure, but using it was no more complex than just using a normal project.

Right now at work I'm banging my head against SQS.