As I posted in the last post, I didn't have much time to update my blog last month (even most of this month), so I hope I could catch up these days and post some more about the on going issues that comes up.

Last month, a gut named Roni Schuetz send me an email regarding my post about Maintaining Data over Multi-Servers (Load Balancing on Web Farm) (direct link here).
Roni is the creator of a project named, Shared Cache which supplies high-performance, distributed memory object caching system, generic in nature, but intended to speeding up dynamic web and / or win applications by alleviating database load. He suggested me to use his project regarding maintaining cached data between multiple servers and I acceded testing it.

By Roni's documentation and project usage explanations the project is friendly usable and for a free-to-use-software I think it is highly recomended using it (or at least testing it).

Unfortunatly (or not), my company (IDT Global) has purchased (an expensive and also a great one) tool called ScaleOut SessionState In order to maintain session data over multiplae servers.

So, if you have an answer regarding this issue or just want to read about it, you can try Roni's indeXus.Net Shared Cache here.

Long time no post, I know... I have some stress at work these couple weeks, we need (I need*) to go on QA these days with the first step of the on working application (doing now some unit tests).

I ment going to Roy Osherove and Danko meeting regarding Agile and Scrum Planning but it didn't turn out, so I listened it through Roy's blog. I must say that I very enjoyed it and there were some things that actually match some of my cases regarding my working.

I Involved with some things that were said there but the most one is the distance issue. I am leading technologicly the web application that we are working on, and the rest of my team (2 software programmers and a project manager) are sitting in the US (Newark). Every evening (my evening - their morning) we are doing a conference meeting, sometimes on phone and sometimes on video and discussing the problems we bumped in, schedules, missions and some code reviews, this meeting is quite good and enable us to catch up on each other and to try manage the process of the working application.

BUT, this distance has a price! This price comes to fruition by time. Sometimes when I have some questions regarding the project spec, or just simple questions that I could get a quick answer from the project manager, I need to note'em and to send an detailed email regaring it.

Roy talked about it in his Scrum meeting introduction and said: "Keep team together, side by side, not even in seperate floors or rooms" and I think it's true, but like every project or something else in life anything has adventages and disadventages; This distance helped me to understand better the flow logic of the application, its functional specifications and more.

So, I'll try to bring in some more Scrum points into my team and project management...