Showing posts with label amazon. Show all posts
Showing posts with label amazon. Show all posts

Tuesday, September 21, 2010

links for 2010-09-21: Amazon Hiding in Plain Sight; PostgreSQL 9.0 released; iPad good for two things; Oracle and HP make up; Unbreakable Enterprise Linux kernel performance doubts

Thursday, July 15, 2010

Amazon further integrates Simple Notification Service with AWS

I've always been interested in messaging systems and had some fun learning about AWS's SNS and then building a simple Cloud Event Processor that utilized it earlier this year.  Amazon had already provided out of the box integration of SNS with the Simple Queue Service (SQS) but has now introduced integration with S3 so that you can get notifications for certain S3 Reduced Redundancy Storage events.

Asynchronous programming at work.  Good stuff!

Thursday, April 29, 2010

links for 2010-04-29: AWS to be as big as Amazon retail?; Steve Jobs on Flash; Backlash against PowerPoint; Flash History

  • Amazon Looks to Widen Lead in Cloud Computing - Opens a new data center in Singapore, but also says "Amazon Web Services can be as big as our retail business, in the fullness of time".
  • Steve Jobs thoughts on Flash - He makes several good points, but calling Adobe closed and proprietary given Apple's tools target a single platform (vs many) and the closed nature of the App Store (vs anyone can create an app without approval) is a bit of the pot calling the kettle black.  And if third party software not taking advantage of new APIs and features is really so terrible, let the market determine that and decide.
  • We Have Met the Enemy and He Is PowerPoint - "Commanders say that the slides impart less information than a five-page paper can hold, and that they relieve the briefer of the need to polish writing to convey an analytic, persuasive point. Imagine lawyers presenting arguments before the Supreme Court in slides instead of legal briefs."
  • Flash History - A good reminder that Flash did fill a need, but he also had a zinger directly at Cupertino: "... a platform with a vendor who gets to decide what’s allowed to run is profoundly uninteresting to me anyhow."
  • News Analysis: Salesforce.com and VMware Up The Ante In The Cloud Wars With VMforce - Good summary.  Pits the Java offerings vs Azure.

Wednesday, April 28, 2010

links for 2010-04-28: Android momentum; Microsoft and Open Source; VMforce; Web vs Enterprise; AWS Presentations

Sunday, April 25, 2010

links for 2010-04-25: Is Apple or Adobe or Google open?; iPhone crimes; Amazon building out capacity

Tuesday, April 20, 2010

links for 2010-04-20: E-commerce witch hunt; ODF plugin no longer free; Oracle Java virtualization on JRockit, not Sun JVM; NoSQL and Cloud; iPhone leak loses customer

Thursday, April 8, 2010

First impressions of Amazon Simple Notification Service

Amazon introduced their new Simple Notification Service (SNS) earlier this week and with a background and interest in integration and messaging I had to take a look.

The sign-up process is simple enough and I added access to it from my existing Amazon Web Services account and was pleased to see that current pricing includes a Free Tier that provides 100K requests and notifications (1K e-mail notifications) for free.  With that, I launched into the getting started guide.

I downloaded the CLI (minor nit, the guide gave the wrong pointer to where to download it, but was easily found), already had Java installed, so I set the required environment variables and was off an running.  There was a mention that the CLI was for Windows and Linux, but I forged ahead on my Mac figuring it would just work, and thankfully it did.

I followed the guide to create a topic, subscribe to it using e-mail, publish a message, and get the notification.  It all worked very nicely and as one would expect.  So, it works, but using a command line tool to send myself an e-mail isn't terribly useful or interesting and if that is all I did, this would be a pretty boring blog entry!  How about something more interesting then?

I have a weather station set up at home along with a web-site for viewing the current weather and uploading historical data to the Weather Underground.  I find myself checking the current conditions periodically, but polling for that kind of thing is a bit cumbersome.  It seems like having a notification pushed to me when certain conditions occur might be more useful and enter SNS to help solve that for me.

So, I wrote a script that I have cron run every 10 minutes that checks the temperature and pressure and if the change is greater than a certain threshold, publishes a notification to my "Weather" topic.  I'm then able to subscribe to the topic so that I'm sent an SMS when a weather notification is published.  Using SNS, I was able to set this up in a matter of minutes and now have something that will just run for me from now on.  Note that I did this on Linux as that is what is running on the machine my weather station is connected to so indeed it does work on both OS X and Linux.

One might ask, why use SNS to do the notification when I could have just had my script do it?  Great question, and if my only goal was to do just this notification for just myself, just hardcoding it in the script would be fine.  But using SNS decouples the components of the application that gives more flexibility and allows the consuming services to be independent of the producer.  It enables new styles of programming centered around asynchronous messaging.

For example, what if others want to also get the notification?  Or if rather than just sending an e-mail I'd like to have a consuming service log the notifications or perform some other processing on the data?  By using SNS to decouple the services, this is easily possible by simply adding subscriptions for each new consumer and I can avoid having to modify or maintain my script with details it really shouldn't be concerned with.

With SNS Amazon has a nice complement to the Simple Queue Service (SQS) that has been around for a little while.  Interested in learning more about asynchronous messaging?  Give one or both a try.

links for 2010-04-08: C overtakes Java; Amazon SNS; Statistics and Data; Oracle and MySQL; iPhone OS 4

Wednesday, March 31, 2010

links for 2010-03-31: Leadership Lessons; Rimini response to Oracle; Gmail and OAuth; Oracle closes loopholes; JumpBox eases apps on EC2; IBM buy Novell?; Apple violated multitouch patent?

Thursday, March 25, 2010

links for 2010-03-25: Redis or SimpleDB?; Oracle extracting revenue from Sun customers; AWS SDK for Java

Thursday, February 25, 2010

links for 2010-02-25: Amazon SimpleDB; SOA and the Cloud; Dual Licensing

Tuesday, February 23, 2010

links for 2010-02-23: Stuck with Oracle or IBM?; Amazon most trusted; Apple in the enterprise

Thursday, October 1, 2009

Amazon Public Data Sets

I follow the Amazon Web Services Blog and recently saw several announcements about new Public Data Sets being available.  What is a public data set you ask?  From the web-site:

Public Data Sets on AWS provides a centralized repository of public data sets that can be seamlessly integrated into AWS cloud-based applications. AWS is hosting the public data sets at no charge for the community, and like all AWS services, users pay only for the compute and storage they use for their own applications.

What is cool about this is that it greatly simplifies getting access to large sets of data that while public in the past, were difficult to work with as you had to download, install, load, and otherwise provide the infrastructure for and manage all the data yourself.

The one that caught my eye was the Daily Global Weather data set.  Now, I haven't used this yet and there are other great resources for local weather station data like the Weather Underground (where I upload my station data by the way), but this is a great way to gain access to a bunch of historical weather data.  Other data sets include census data, Wikipedia data, geographic data, and more.

One drawback for data sets that are continuing to be updated each day, like historical weather data, is that you aren't accessing a continually updated data store, rather you are creating your own EBS volume from a snapshot.  This means (if I understand all this correctly) that if you need the most recent data, the snapshot must be updated regularly and you would have to update your EBS volume from it manually.  Or perhaps there are tools to assist with that.

All in all, a useful service, and a great move by Amazon to drive more users to EC2.