Throwback to early days of #ROR ~ circa 2007/08
Ruby's single threading was leading to serious scalability challenges at SlideShare (also Twitter etc). The word on the tech street - "RubyOnRails ain't enterprise-class. These platforms won't scale".
#RubyOnRails #Rails #Ruby /1
Ruby's single threading was leading to serious scalability challenges at SlideShare (also Twitter etc). The word on the tech street - "RubyOnRails ain't enterprise-class. These platforms won't scale".
#RubyOnRails #Rails #Ruby /1
ROR was optimized for "developer efficiency & happiness".
That's what endeared it to Web2.0 startups - iterate, build fast & break things, think MVP, Agile, Lean... get to product-market-fit ASAP
Whether it could deliver at enterprise scale like java, dont net was untested /2
That's what endeared it to Web2.0 startups - iterate, build fast & break things, think MVP, Agile, Lean... get to product-market-fit ASAP
Whether it could deliver at enterprise scale like java, dont net was untested /2
I do remember - the cacophony about the supposed "non-scalability of ROR" did give us nervous moments at SlideShare.
AFAIR it was NGINX that played a key role in helping address ROR's scalability issues gradually!
@jboutelle..... is that correct? /3
AFAIR it was NGINX that played a key role in helping address ROR's scalability issues gradually!
@jboutelle..... is that correct? /3
My learning from that episode - startups often have to choose between "proven vs/ un-proven" paths.
This could be pieces of technology, people, strategies, tactics etc. /4
This could be pieces of technology, people, strategies, tactics etc. /4
Its imp to consider role of momentum (traction) in your choice. Thats what helped ROR, it had momentum & the dev community rallied behnd it
This isnt diff frm how VCs look for evidnce of "traction" when evaluating startups
The shape of the growth curve heals many ailments:) /5
This isnt diff frm how VCs look for evidnce of "traction" when evaluating startups
The shape of the growth curve heals many ailments:) /5
