Discuss New Concept,New Technic,New Tools, Including EAI,BPM,SOA,Tibco,IBM MQ,Tuxedo, Cloud,Hadoop,NoSQL,J2EE,Ruby,Scala,Python, Performance,Scalability,Distributed,HA, Social Network,Machine Learning.

Quote

Mar 122011
 
 Tweets of Gold:  March 12, 2011  Posted by on March 12, 2011 at 12:01 pm Quote Tagged with: , , ,  No Responses »
  • @timoreilly: When hardware became commoditized, software was valuable. Now that software being commoditized, data is valuable. #strataconf
  • @coldfusionPaul: “Write someone a query, they’ll go away for a day. Teach someone to query, they’ll just go away.” so, I use #NoSQL 555
  • @squarecog: To go *really* fast, you want to get rid of spokes in your wheels, and ditch tires. Also, turning is overrated. #nosql
  • @Ryan Tomayko: Frameworks don’t solve scalability problems, design solves scalability problems. Via @GregSkloot
  • @zuno: The golden rule of scalability: “it can probably wait” look for other areas to save resources.
  • @bihzad: joinserv hit a scalability wall, but I’m pretty sure I can climb over it with multiprocessing
  • CarryMillsap: You can’t hardware yourself out of a performance problem you softwared yourself into.
  • @juokaz: schema-less databases doesn’t mean data should have no structure
  • @jreichhold: One thing working at Twitter teaches me daily is that all scale is relative. What seemed impossible last year is now the daily case.
  • @jkalucki: Throwing 1,920 CPUs and 4TB of RAM at an annoyance, as you do. @jointheflock
  • @AmyDeLong: Walked into a starbucks and overheard 3 separate discussions all on scalability. #firstworldproblems #onlyinsf
  • @chvest: You may not need “high” scalability, but you should still consider your growth rates and prepare.
  • @hofmanndavid: Performance and scalability anxiety makes developers want to catch the flying butterflies
  • @tivrfoa: “Scalability solutions aren’t magic. They involve partitioning, indexing and replication.” Twitter engineer
  • @Alan Perlis: Fools ignore complexity; pragmatists suffer it; experts avoid it; geniuses remove it.
  • @labsji: If SQL is an abstraction of Big machines….NoSQL is an abstration of distributed computing.
  • : man this eventual consistency #nosql thingy makes #facebook even more annoying. “you have a new comment, no you dont”
  • @dmalenko: It is cool to sit by the ocean, oversee the sunset and think about scalability models for a web app
  • @detroitpro: I have to admit; sometimes I think “This would be easier with a SQL DB” #NoSQL #NotOften #ComplextRelationships #FindingRootObjects
  • @jkalucki: Getting just 100 servers to work together for the first time is so ridiculously complicated. Horizontal scaling doesn’t scale.
  • @simeons: Yahoo’s scalability is drivem by lots of asynchronous processing. “You learn to love it.” — @rstata Yahoo’s CTO
  • @jerng: Reading up on scalability. WHY THE HELL FOR? Because I want to know the future.
  • @freerangedata: The #nosql options are the micro brews/craft beers of data stores. So many good ones, so little time to try them all.
  • @edward_ribeiro: Soon, Darwinism will start to play its role on #NoSQL systems. You know, only the fittest will survive.
  • @connectionreq: I’m always wowed when I hear how Facebook abuses their MySQL databases in crazy ways
  • @louismrose: This is the kind of scalability we should be working on… http://yfrog.com/59qb0oj
  • @old_sound: Somebody make me a t-shirt that says “I’ve read the CAP theorem and I liked it”
  • : How relevant do I think the CAP theorem is? Not at all. I honestly hate conversations where anyone talks about crap.. cap, sorry.
  • @humidbeing: If you hit limits of mysql, why reinvent the wheel by rolling your own solution when DBs like MS SQL and Oracle have proven scalability?
  • Ayende Rahien: You saved 5 cents, and your code is not readable, congrats!
  • georgebarnett: I read High Scalability for useful articles about large scaling. Sadly though, nothing useful ever shows up. #NoLongerBothering
  • northscale: wow that is fast! :) RT @cgoldberg: was just running > 100k ops/sec against my 2-node #Membase cluster… zazooom #nosql
  • turbofunctor: The root of many (horizontal) scalability problems is an application level access to a writable filesystem. (Thus, #appengine.)
  • gwenshap: highscalability.com is like Vogue for IT operations. Map-reduce is so last season.
  • lenidot: with 12 staff, @tumblr serves 1.5billion pageviews/month and 25,000 signups/day. Now that’s scalability!
  • jmtan24: Funny that whenever a high scalability article comes out, it always mention the shared nothing approach
  • mfeathers: When life gives you lemons, you can have decades-long conquest to convert lemons to oranges, or you can make lemonade.
  • OyvindIsene: Met an old man with mustache today, he had no opinion on #noSQL. Note to myself: Don’t grow a mustache, now or later.
  • vlad003: Isn’t it interesting how P2P distributes data while Cloud Computing centralizes it? And they’re both said to be the future.
  • kbsingh: I dont understand why some developers think its ok to leave operations people out of scalability decisions
  • karmazilla: I find it a little odd when a database claims to support “massive scalability” when it is not distributed.
  • pcapr: OH: teenagers are eventually consistent
  • tv: Verb suggestion for the act of mapreducing data: “marinating”. “Then we marinade it to get the n-gram frequencies.”
  • bryanlatten: Nothing like a million caching layers to screw up an already complicated deployment. Thankfully, there is beer.
  • jkalucki: Twitter isn’t down, you are just using the wrong access methods…
  • andyedinborough: I don’t mean to hate, but why would I give up performance and scalability for a dynamic language? Honestly, I don’t get it.
  • AsitSinha: It’s amazing…. to see the absence of an understanding of how capability plays a role in scalability.