email
twitter
linkedin
flickr
Showing posts with label google. Show all posts
Showing posts with label google. Show all posts

Wednesday, April 28, 2010

Spam? What spam?

Today I was writing up what I hope will be a semi-regular email to the users of the company I work for detailing some new developments we had completed in the IT department. I wanted to include a little interesting statistic at the end so I logged into our Postini account to see how much mail we were processing monthly and how much spam we were blocking. No big surprise, we were running at about 80% of our inbound mail being blocked as spam. This is actually below some of the statistics showing as much as 95% of all email being blocked. The impressive statistic was that one mailbox accounted for 25% of all of our email while still having 93% of its mail blocked.

All of this made me think about the fact that I pretty much never see a spam message reach my inbox on Gmail or my work account as a result of these services. Google does it for me for free. For as easy as it is to block and as much spam as is being sent, how is it even profitable these days to send spam? There must be a significant number of people still, to this day, not using a high quality spam fighting service. By the way, if you happen to be in the market for one, head over to Purity Networks and take them up on their free user offer. This is a great alternative to services like Postini for your business.

Along these lines, I still cringe when I see people change their email because they changed ISPs. Since the advent of Gmail and the like, why does anyone continue to use substandard email or change their email more than once making a move to an ISP independent service? Google apps has even made it beyond simple to set up your own custom domain riding on their systems. Maybe it is just a lack of knowledge that keeps people tied to their ISP email. What do you think?

Saturday, April 26, 2008

Breaking up with Google App Engine

Sorry Google. It's you, not me.

Perhaps I'm not the target developer for Google App Engine but it seemed like it. I run hsxworld.com, a little community site built around the Hollywood Stock Exchange Game. It pretty much runs itself on a webhost with a database but lately my backend software, PHPnuke, is aging.

Along comes Google, with their new fangled App Engine that seems a perfect fit. Dump the stock data plus other stuff into it, build a few functions to return some data, and I have a nice scalable engine to host the data on. I even had some fun learning Python for the first time as well as exploring some AJAX. Even better, I could even design it so that other community sites could grab the data AJAX style and maybe give a little back.

What I found quickly was that the BigTable database engine behind it was either not well suited to what I was doing or I was doing things all wrong. I even went so far as to really AJAXize my code to fire off many transactions instead of large monolithic queries. Nothing seemed to help. Simply queries like finding 20 or 30 records from a 300-400 row table took longer than they should. More optimizing, and I was able to get it reasonable (see here) but yet the backend logs still complained that I was using too much CPU.

Too much CPU on a 30 row query? Egad.

So, I'm breaking up with Google App Engine. I'll just have to either upgrade my PHPnuke or abandon it for some straight PHP+MySQL.

Wednesday, April 16, 2008

Head in the clouds

So I managed to get signed up for one of the free accounts on the Google App Engine. It is basically a distributed computing cloud that lets you write Python applications that run on Google's massive infrastructure. So far it has been a great experience learning a bit about Python and playing around with what the engine can do. I was considering using this as a data service platform for hsxworld.com since I need to do a bit of rewriting there. More on this later.