[Jim Robinson]

I think that’s the same conclusion we’re coming to. Very likely a database/software/hardware design vs actual usage issue. And there is no quick cure. A complete redesign and rewrite using all newer technologies in hardware and software ought to do the trick. Thankfully, I’ve been working on a new system using AJAX based techniques for a couple years (in my spare time) and even have a bare bones prototype working, but it’s months away from even being ready for beta testing. And John is beginning to think Cloud. Who knows? We may be rolling out something brand spanking new in the months ahead. But it’s going to be hell around here for the next week or so. Praying we make it.

[onyx]

Thanks very much, dearest Jim.

Just so you all know: Offers of help have not be spurned. Jim and John are fully aware of the problems and of the solutions, but like Jim has explained, solutions are not instant and they are working as fast as humanly possibly.

I know we’re all exasperated at times and grow impatient, but FR is our home, so please know that while we want an immediate fix, nobody wants it more than Jim and John!

Thank you all for your continued support and patience.

[tomkat]

Thanks for that, boss !

[RedMDer]

(in my spare time)

LOL! Where in the world do you find spare time? You are are almost always here in the Best Conservative Site on the net that you founded.

[mylife]

While the problems have become frustrating, this is still the best conservative news aggregate and forum out there.
A new design looks like it may be inevitable at some point just to keep up with technology.
I just hope that we can save the archives somehow.

[justlurking]

And John is beginning to think Cloud.

I think that the cloud is the way to go, because you can scale up and down your infrastructure as needed. But, presuming that the problem is indeed the database, you'll have to re-architect the database.

SQL doesn't scale easily, unless you spend a bunch of bucks for an Oracle Enterprise server. However, a NoSQL database would be easily scalable to multiple nodes, and you can add them or subtract them as necessary to meet peaks and valleys in demand.

Aside from the implementation effort, there's the cost. Amazon's EC2 cloud can do everything you want, and more -- but at a price.

[Syncro]

Thanks Jim and John.

Looks like some good improvements in the future.

Keep up the good work, we appreciate all that you do.

Free Republic is da bomb!

[Alas Babylon!]

I’ve been working on a new system using AJAX based techniques for a couple years (in my spare time) and even have a bare bones prototype working, but it’s months away from even being ready for beta testing.

It's nice to hear about some of the "older" designers keeping their skills sharp! ;-)

Cloud may be the way to go; you don't have to worry about the server iron, backups, data protection, power, cooling, etc.; great to offload that to somebody else.

Still, what about content and politics? Most of the bigger Cloud providers are also very Left leaning...

Remember when the NFL wouldn't let Rush Limbaugh buy 1/6th of the St Louis Rams? Would they want Free Republic on their datacenter?

[mlo]

"I think that’s the same conclusion we’re coming to. Very likely a database/software/hardware design vs actual usage issue. And there is no quick cure. A complete redesign and rewrite using all newer technologies in hardware and software ought to do the trick. Thankfully, I’ve been working on a new system using AJAX based techniques for a couple years (in my spare time) and even have a bare bones prototype working, but it’s months away from even being ready for beta testing. And John is beginning to think Cloud. Who knows? We may be rolling out something brand spanking new in the months ahead. But it’s going to be hell around here for the next week or so. Praying we make it."

I would only consider those things if caching has already been addressed. Lots and lots of caching.

[BuckeyeTexan]

Cool.

[BuckeyeTexan]

This too shall pass. We’ll get through it. It might make us gray-headed and grumpy, but we’ll get through it.

[Mama_Bear]

Thanks for pinging me to this discussion, Jim. Good luck with that new prototype program. I think it looks great, and promising! I know you have been working hard on it and you are anxious to get it up and running. We are pulling for you. As far as the next couple weeks go, hey, it will be what it will be. This too shall pass. :-)

[Lazamataz]

I think that’s the same conclusion we’re coming to. Very likely a database/software/hardware design vs actual usage issue. And there is no quick cure. A complete redesign and rewrite using all newer technologies in hardware and software ought to do the trick. Thankfully, I’ve been working on a new system using AJAX based techniques for a couple years (in my spare time) and even have a bare bones prototype working, but it’s months away from even being ready for beta testing. And John is beginning to think Cloud. Who knows? We may be rolling out something brand spanking new in the months ahead. But it’s going to be hell around here for the next week or so. Praying we make it.

Hey Jim! A few thoughts:

• As you already well know, AJAX is a technique and the language you choose implements that. I might be wrong but I think you mentioned Javascript at the Shoot. Pros and cons to Javascript, if that's the chosen language. I've seen some very highend systems written entirely in javascript but obfuscation is an issue. You have to issue the source code to the browser (though you can obfuscate it somewhat by stripping meaningful variable names and method names) but still, you have to issue the javascript for the browser to be able to work with it. Javascript also lends to being unstructured, it isn't a Strongly-Typed language (you can change an int variable to a string variable on the fly) and does not lend itself well to Object Oriented Programming.
• I've looked a lot at the various ways to host what I have in mind for the system... Linux running Mono (which is a Common Language Runtime interpreter of the Bytecodes that .NET emits) is a very good solution. But I spoke last night to a fellow named David C., he was my boss at a former company, who then went on to found a very successful Enterprise Solution company. He actually convinced me that Cloud was the way to ensure -- and remove from the variable list -- hardware scalability issues.
• I'm a big proponent of dot Net. It's a VERY easy to maintain and VERY easy to debug language, when you write OOP code. However, I just might open my mind to other languages.
• I've collected a series of desired features from a variety of users. I can share those with you.
• Should my efforts be fruitful, I will gladly release source code to you guys, to modify and use as you will. Consider it an in-kind donation. I would like to be thought of as one of the maintenance crew, in that case. Of course, all standards of professionalism would apply.