Please create an account to participate in the Slashdot moderation system


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 Internet speed test! ×

Comment Too late (Score 0) 224

Already have one. Unfortunately it's over PPPoE and most consumer-grade routers can't handle that magnitude of data over PPPoE. If I want the full speed I have to plug the cable straight into my computer or spend a ton of cash on a router that can hopefully handle it. Downloading at 40 MBps is pretty nifty though.

Comment Re:Ooooh shiny (Score 0) 272

The problem isn't that NoSQL is bad - it's not. The problem is that the scale of data needed for its benefits to outweigh its shortcomings is, well, staggering. For anything less, a well configured RDBMS will be right there performance-wise and will give you the added safety measures that only decades of real-world experience can provide. I can understand wanting to try something different. NoSQL is very interesting in that regard. If you're talking about using it in a personal or non-critical work project, then by all means, go right ahead. But if you want to build a critical project and take it to production, old school is the way to go.

Comment Ooooh shiny (Score 0) 272

I'm with the guys claiming premature optimization. I think you've been duped by the legion of NoSQL evangelists into thinking RDBMS are old, slow and obsolete and if you put a few thousand rows into a few tables they'll bog down and take minutes to query it. Here's a spoiler: they're wrong. I think you'd be amazed just how robust and fast Postgres, MySQL and MS SQL can be if configured and used correctly. The question NoSQL actually answers is "would you sacrifice atomicity and some consistency for a much higher data throughput?" I work on projects that have to manage sizable chunks of data every day and in my experience NoSQL is only an option after you've exhausted all other avenues. If you've designed a bulletproof database schema, optimized all your queries to the bone, created every possible index on every possible table, partitioned your database files and even thrown hardware at it and you still have issues, then NoSQL might be your salvation. Otherwise, stick to what everybody else is using.
The Military

United States Begins Flying Stealth Bombers Over South Korea 567

skade88 writes "The New York Times is reporting that the United States has started flying B-2 stealth bomber runs over South Korea as a show of force to North Korea. The bombers flew 6,500 miles to bomb a South Korean island with mock explosives. Earlier this month the U.S. Military ran mock B-52 bombing runs over the same South Korean island. The U.S. military says it shows that it can execute precision bombing runs at will with little notice needed. The U.S. also reaffirmed their commitment to protecting its allies in the region. The North Koreans have been making threats to turn South Korea into a sea of fire. North Korea has also made threats claiming they will nuke the United States' mainland."

Slashdot Top Deals

"The eleventh commandment was `Thou Shalt Compute' or `Thou Shalt Not Compute' -- I forget which." -- Epigrams in Programming, ACM SIGPLAN Sept. 1982