logoalt Hacker News

ChicagoDaveyesterday at 5:36 PM2 repliesview on HN

This is exactly how tightly coupled, unmaintainable software is constructed.

By picking the tools before understanding the model and building bespoke architecture.

You pick the tools that the business model requires. It might be a relational data store. It might not be. You might want an event store. You might want to reduce costs with lambdas and DynamoDB. You may need a pub/sub event broker.

The OP clearly loves Postgres. Cool. They also have limited experience with complex systems architectures because if they had that experience, they would have never written this article.


Replies

groundzeros2015today at 3:40 AM

> You might want to reduce costs with lambdas and DynamoDB.

I don't think that's ever saved money.

> because if they had that experience, they would have never written this article.

That's not true.

show 1 reply
ballon_monkeyyesterday at 11:45 PM

> This is exactly how tightly coupled, unmaintainable software is constructed.

No. If you're struggling to build software against a DB and then abstract parts to use Redis or ES or whatever in the future, that's kinda a skill issue you or your team have with building poor software to begin with. Nothing to do with using a DB for multiple things like a Queue/Search etc.