Use or Read RSS Feeds Still? Here’s Your Tech Blogs

This is another one of those lists I’ve started putting together. I wanted to get it out there to the public. It all started with Hadi @HHariri converting his blog from WordPress to Jekyll using Github Pages. I’ve wanted to get a solid list of top blogs. One’s that have great content, solid writing, technical and mixed topics of tech, leadership and related to technology blogs. If you’re not reading blogs these days, now is as good a time as any to click the Feedly logo to the right and go get subscribing and reading! If you are reading some blogs, add them to the list!

To check out Hadi’s blog navigate over to http://hadihariri.com/. For a kick start yourself, check out my entry on Bringing it All Together, Bringing to Life an Open Source Software Project via Github & Jekyll – Part 1.

To help out with the blog list, add a blog or three that you read regularly. Cheers and thanks!

Orchestrate.io JavaScript Client Library

Today I’m starting a project working with Orchestrate.io’s API & open source software collaborations. More about the project in a moment, let’s get up to speed on what I’ll be including in this project. My main focus is to build a client library to access Orchestrate.io. During building this I’ll dive into the key value, graph and other storage mechanisms that the client library will provide. Beyond that, I’ll take a stroll through building an NPM library and the pertinent JavaScript the library. So buckle up, we’re going on a code slinging hash writing hacking session.

Over the course of putting together this material, I’ll be posting most of the core material on Orchestrate.io’s blog, so subscribe for updates as they come out. Feedly is a good option, connect via searching for “orchestrate.io” or navigate over to the Orchestrate.io blog itself. 😉

Project Effort Context

During building the client I’ll take a dive into who, what, where, when, why and how to interact with the various data structures. I’ll aim for the client to follow the model of the existing Go Client Library that is available at Orchestrate Go Client on Github. It follows a basic model as shown below in Go language.

[sourcecode language=”cpp”]
c := client.NewClient("Your API Key")
// Get a value
value, _ := c.Get("collection", "key")
// Put a value
c.Put("collection", "key", strings.NewReader("Some JSON"))
// Search
results, _ := c.Search("collection", "A Lucene Query")
// Get Events
events, _ := c.GetEvents("collection", "key", "kind")
// Put Event
c.PutEvent("collection", "key", "kind", strings.NewReader("Some JSON"))
// Get Relations
relations, _ := c.GetRelations("collection", "key", []string{"kind", "kind"})
// Put Relation
c.PutRelation("sourceCollection", "sourceKey", "kind", "sinkCollection", "sinkKey")
[/sourcecode]

I’ll be working on this client, but don’t hold back on me, feel free to jump in with some of your own code or telling me I wrote some code wrong or whatever. I’d gladly accept any committers jumping in to help out. The more we all work together the more useful information I can provide during this project.

Once this project has produced a workable client pending interest from the community I’ll put together some material about where, how and some best uses around using the client in your Node.js Application. Even prospectively build a JavaScript client side library prospectively for use with Angular or other popular client side libraries.

References

AWS, WordPress, Windows Azure, Clouds, and More…

I’ve been looking into getting a blog, specifically WordPress, into the cloud.  Of course the first two I take a look at are Windows Azure and AWS.  This is what I’ve found so far.

Windows Azure

Windows Azure is easy enough, sort of, but distinctly limits the control and abilities of the actual blog.  This is primarily because of the way one has to host a blog, and the software just isn’t really built to take advantage of the platform specifically.  In other words, WordPress isn’t really built around horizontal scalability.  Also one has to run WordPress in a CGI Instance, not exactly ideal either.  It works, and really does work well, but there are just options that aren’t available in this situation.

The other issue is that a single running CGI Role is going to run you around $100 bucks a month.  I’ve checked and if you push off the entries into a Windows Azure Table Storage area, that’ll easily break past that $100 bucks into the $110-200 range or higher.  It all really depends on how many transactions and views your site is getting.  If you really necessitate Table Storage vs. a traditional relational data store for your blog, I seriously doubt a couple hundred bucks will be an issue.  In all reality, if you’re using the Table Storage you most likely should be in the traffic range that would run you about $1000 bucks a month or more, in each geographic area.

Amazon Web Services

AWS is however a different beast altogether.  First, running an EC2 instance you can get everything running that you need.  The data store for the entries and also gain access to a level that allows you to add plugins and all the other features of WordPress.

The pricing on Amazon gets a lot better too.  One can get the reserved instance for $350 bucks a year (or $227.50 for Linux/UNIX).  That enables one to install WordPress with total control for about $30 bucks a month.  Considering the redundancy, uptime, and general availability and performance of the cloud that is a really decent price.  Even if one gets some heavy bandwidth usage, the cost for that shouldn’t go above a few dollars.

Summary

At this time, if you want some cloud computing power behind your blog, AWS is the clear winner in price and performance!

A few reference links: