2 ms·
I think that’s the way to go. Start with Postgres and only if there are problems, then think about something more specialized. Same for microservices. Start sim
by vjvjvjvjghv 2mo ago
I think that’s the way to go. Start with Postgres and only if there are problems, then think about something more specialized. Same for microservices. Start simple and introduce a service when really needed.
I hate it when people already start out with 10 or more different systems/services for a few messages per second.
- cheikhcheikh 2mo agoit's not the way to go if you hit the limits very quickly and have to waste immense time migrating.
- vjvjvjvjghv 2mo agoFrom my experience the limits are way higher than people think.
- cheikhcheikh 2mo agofrom my experience they're actually much lower than people think, especially when using Postgres for things it's not well-suited for like queuing, and the problem is you rarely can just throw more hardware at it to solve the problem and it's really not a good place to be.
- egwor 2mo agoI think that using the right tool for the job is important and saves a lot of time in the long run. There are expensive headaches that we have to resolve.
- vjvjvjvjghv 2mo agoI never know what to think about the phrase “ right tool for the job”. It almost feels like a platitude at this point.
- inigyou 2mo agoPostgres is the right tool for most practical data storage jobs.