Scaling?
I have to rant about this.
I know people think wether or not a given..what’s the right word…develomental approach..yah..wether or not a given developmental approach to a problem is “scalable” or not. Ever since I decided to skinny dip in the pool known as Ruby on Rails I’ve been reading countless blogs/forum posts/tattoo’s on the ass of a fat girl/etc about how Rails “doesn’t scale” - are these people INSANE?
If there was a fucking “scalable” silver bullet approach to application development - everybody would be using it. _NOTHING_ fucking scales..especially when you leave what you intend to scale undefined.
First of all, if you’ve been fortunate enough to work on a project that runs INTO scaling issues, you finally realize scaling is turning into a buzzword. Anytime I run into what people consider a scaling issue it’s REALLY just a design or architectural bottleneck..it could be your ass end database..maybe it’s parser is fucking up OR statements in your WHERE clause..perhaps HAVING is better for your application..
MAYBE the language the app is written in is interpreted and a tad slower than need me..perhaps there’s a fix.
Maybe YOU layed the design out in a fashion that lends itself to failure.
I’ve ran into ALL of the above..and NEVER once could I have said “Given the same set of problems, if I would’ve used Java or Django/Python - this would not have happened”
As you experience growth, you’ll run into issues that you can define as “an issue of scalability” - you can fix it..you may need to handle it with hardware, refactoring, or sexual relations with a chimp - but YOU CAN FIX IT.
Does Java scale? no
Rails? no
COBOL? no
A Prius? no
Metal music? Yah..actually music DOES scale due to “fusion”. Mix Jazz & Metal..boom..music has just scaled to take care of the needs of weirdos like me.
Mix Rails with Java? Fusion - it might solve a problem..it might piss you off..who knows.
bap.
3 years ago