Monday, January 12. 2009PostGIS on Windows 2008 Server in the CloudGoGridWell we knew this day would come when we would have to start experimenting with Clouds. Now it seems a lot more cloud providers are coming on line. For our first experimentation we chose GoGrid because they offer a free 1 month/50$ trial plus we needed to test out Windows 2008 Server as well as Linux and they had an offering for both where as Amazon seems to only offer Windows 2003 and its very new. We were hesitant to go the Windows 2008 Server 64-bit route since we aren't sure how well PHP works in 64-bit IIS 7 and in general I've had nightmares with IIS in 64-bit mode e.g. the fact that they will not be releasing 64-bit jet drivers and in many cases there is no alternative in the ADO.Net world and so forth. The hardest challenge turned out to be getting PHP to run in Fast-CGI under IIS 7.0. As the title suggests PostGIS 1.3.5/PostgreSQL 8.3 seems to work just fine under Windows 2008 Server (well at least 32-bit). Took me all of 10 minutes to download, run the application stack builder. Loading my data took a bit longer, but that is not surprising. Windows Server 2008 doesn't look all that different from Windows 2003. There is some cross-breeding look between it and Vista, but at least I can more or less find things. Couple of things I liked about GoGrid
What I didn't like
Amazon EC2I hate getting my information from a vendor site, but GoGrids article on Cloud Centers seemed to be a pretty decent one and a fair comparison Cloud Centers in the Sky. Though I still felt confused, but I blame this on my general lack of comprehension. The main thing I got out of it is that Amazon EC2 is very proprietary and GoGrid is built on standards. Being proprietary is not a bad thing per se if it becomes a standard. I think many good things start out life being proprietary. We have yet to try Amazon EC2 and reading their documentation does not give me a warm and fuzzy feeling. Sounds like a lot of AM image configure upload this and that, API to figure out IP and this and that. Doesn't sound like their exists a calming wizard to guide me thru the process. The fact that I can't picture in my mind what is going on is also not very comforting. I hate adopting technologies I don't at least partially understand. Am I wrong in saying they do not offer a free trial to test this out? What I do gather from reading Amazon and even reading GoGrids comparison of themselves against Amazon EC which I like: Good
Trackbacks
Trackback specific URI for this entry
No Trackbacks
Comments
Display comments as
(Linear | Threaded)
I think you will find Amazon AWS a bit more flexible and perhaps less expensive. I've tried both. The memory of GoGrid's entry system is a bit skimpy. AWS small Windows EC2 runs $0.125/hr but the same amount of memory on Gogrid is $0.19/hr.
If you plan to experiment with AWS there is a just released Console that makes life easier for a noobie experiment.
http://aws.amazon.com/about-aws/whats-new/2009/01/08/announcing-the-aws-management-console/
Some advantages I've found with AWS in addition to building your own private template AMIs:
1. EBS lets you separate PostGIS data from the EC2 instance and allocate to any instance you want
2. EBS lets you backup data with snapshot to S3 - S3 is a redundant store with higher reliability
3. ElasticIP lets you have equivalent of a static IP that can be switched to whatever instance you wish without waiting for DNS propagation.
4. If failover is an issue you can have multiple EC2/EBS instances in different geographics zones.
Randy,
Thanks for the above. I guess I really have to check out Amazon EC2 now.
I tested this out a couple months back and followed the same path you followed with GoGrid. I also tested using zigGIS on the client side to directly edit my spatial tables in the cloud via ArcMap. It worked well. I would be curious to hear feedback from folks who have tried this with EC2.
|
OSGEOCalendar
Categories![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||
