Technology Update
In the past few weeks, we’ve had a hard time keeping a constant flow of communication with our authors — largely because of all of the scaling issues we’re working hard to address.
Our web development projects are split in 3 categories:
1) Dangerous threats that need to be addressed.
2) Adding new functionality into the current core of our site.
3) Preparing the database and webserver for scaling
One positive thing that is happening is that we are making progress on becoming a distributed computing site — meaning that we are learning how to split up the load across multiple servers that do the same tasks.
We already have multiple servers that pull off the EzineArticles experience (web, database, list, dns, and email), but soon we’ll have multiple dedicated servers that are designed to take portions of the web and database load.
High on our priority list is the implementation of our first load balancing switch along with 2 more dedicated servers, getting a new internal search engine back online that doesn’t cause brownouts or blackouts during its indexing activities, the addition of almost 40 new sub-categories and training all of our new full and part time associate editors.
I apologize for the bumps along the way. Anytime we enhance or improve EzineArticles.com, due to the sheer complexity of this site, we’re constantly vigiliant for unintended consequences when improvements are added.
These new features will be incredible and as I water the EzineArticles.com site pass thru 100,000 articles and 15,000 authors and thousands of Ezine Editors and watch all the articles appear across the Internet on RSS all I can say is WOW. Soon the EzineArticles site will need the Blue Gene Super Commputer L to handle. It is truly amazing how far this site has come and it is kind of daunting to see how far it is to still go on its journey. Glad to be part of the team as an Author, I think we all are. I wonder how the other authors feel about the accomplishments made and the future in Article Marketing and EzineArticles.com
[Reply]