Re:Lessons Learned from Payments Startups
by rrr_oh_man on Thursday February 08, 2024 @04:25PM
(#39307941)
> And it avoids the issue of you wasting limited write I/O on a non-priority task.
Is it really an issue, though, in most cases?
Re:Lessons Learned from Payments Startups
by threeseed on Thursday February 08, 2024 @08:09PM
(#39310113)
For a database. Absolutely.
Re:Lessons Learned from Payments Startups
by anonzzzies on Thursday February 08, 2024 @09:29PM
(#39310724)
In how many instances though? This sounds like premature optimising. We are not all Stripe; many companies making millions, but not billions, would have an easier life without doing more work or paying a fortune to niche saas companies for these type of things.
Re:Lessons Learned from Payments Startups
by rrr_oh_man on Sunday February 11, 2024 @02:05AM
(#39333142)
Food for thought:
Re:Lessons Learned from Payments Startups
by pgr0ss on Thursday February 08, 2024 @05:42PM
(#39308811)
Hi, I’m the author of the blog post.
> And it is bizarre to me that you could run a payments system without high-availability or immutability at its core.
I’m not sure what you’re referring to here as my post didn’t really go into these topics.
> Also putting logs in a database alongside your core data is such a bad idea.
I’m not suggesting putting all logs into the database. I’m suggesting that for a certain type of info (that is often logged), I find it more useful to put it in the database instead.
And it is bizarre to me that you could run a payments system without high-availability or immutability at its core.
Also putting logs in a database alongside your core data is such a bad idea. There are plenty of solid, proven systems for log management that allow you to correlate against other databases. And it avoids the issue of you wasting limited write I/O on a non-priority task.