3 ms·
Why did you go for Ruby instead of PHP? Would you have had the (roughly) same database issues if you didn't have that many writes to the db?
by iconfinder 15y ago
Why did you go for Ruby instead of PHP?
Would you have had the (roughly) same database issues if you didn't have that many writes to the db?
- jrirei 15y agoWe did go for Ruby in order to increase developer productivity (having a very small team of just two developers), and good code quality/high test coverage. We were sure we needed to refactor a lot later on. So Ruby seems like a good choice. But Ruby is NOT good at waiting no a database / network latency. But I guess with PHP we would have had exactly the same problems.
- iconfinder 15y agoDid you compare bare bones PHP with Ruby or PHP with a library such as Zend? I curious because I'm considering recoding a large part of a website and are trying to avoid scaling issues. Thank you for the answer.
- deleted 15y ago[deleted]