Raven DB, A Kick Starter using Tier 3 IaaS

I’m putting together a pretty sweet little application. It does some basic things that are slowly but surely expanding to cover some interesting distributed cloud computing business cases. But today I’m going to dive into my Raven DB experience. The idea is that Raven DB will act as the data repository for a set of API web services (that seems kind of obvious, I state the obvious sometimes).

The first thing we need is a server instance to get our initial node up and running. You can use whatever service, virtualization tools, or a physical server if you want. I’m going to use Tier 3’s Services in my example, so just extrapolate for your own situation.

First I’ve logged in to the Tier 3 Control Site and am going to create a server instance.

Building the Tier 3 Node for Raven DB

Creating the Server Instance (Click for full size image)

Creating the Server Instance (Click for full size image)

Next step is to assign resources. Since this is just a single Raven DB node, and I won’t have it under heavy load, I’ve minimized the resources. This is more of a developers install, but it could easily be a production deploy, just allocate more resources as needed. Also note, I’ve added 50 GB of storage to this particular instance.

Setting Resources (Click for full size image)

Setting Resources (Click for full size image)

Now that we’ve set these, click next and on the next screen click on server task. Here add the public IP option and select the following services to open their ports.

Setting up a Public IP and the respective ports/services (Click for full size image)

Setting up a Public IP and the respective ports/services (Click for full size image)

The task will display once added as an item on the create server view. Once that is done, click create server so the server build out will start.

Creating the Server (Click for full size image)

Creating the Server (Click for full size image)

Now log in with RDP to start setting up the server in preparation of loading Raven DB. The first thing you’ll want to do is go ahead and get Windows Update turned on. My preference is to just turn it on and get every update that is available. Once that is done, make sure to get the latest .NET 4 download from Windows Update too.

Getting Windows Update Turned On (Click for full size image)

Getting Windows Update Turned On (Click for full size image)

Once all of the updates are finished and .NET 4 is installed we’ll get down to the business of getting Raven DB Installed. In this specific example I’ll be installing the Raven DB as a windows service, it however can be installed under IIS so there are many other options depending on how you need it installed.

Installing Raven DB

To get the software to install, navigate over to the Raven DB site at http://ravendb.net/ from the new instance we’ve just spun up. Click on the Download button and you’ll find the latest build over on the right hand side. Click to download the latest software package to a preferred location on the system.

Raven DB - Open Source 2nd Generation Document DB (Click to navigate to the site)

Raven DB – Open Source 2nd Generation Document DB (Click to navigate to the site)

Once you’ve downloaded it (I’ve put my download in the root R:\ partition I created) unzip it into a directory (I’ve just unzipped it here into R:\ to make the paths easy to find, feel free to put it anywhere you would prefer. In our Tier 3 environment the R drive is on a higher speed, thus higher IOP drive system, thus the abilities exceed your standard EBS/AMI or S3 style storage mechanisms.).

Saving the Raven DB Download (Click for full size image)

Saving the Raven DB Download (Click for full size image)

Saving to R:/ (Click for full size image)

Saving to R:/ (Click for full size image)

At this point, open a command prompt to install Raven DB as a service. Navigate to the drive and folder location you’ve saved the file to. Below I displayed a list of the folder and files in the structure.

CLI actions (click for full size image)

CLI actions (click for full size image)

Once you’re in the path of the Raven.Server.exe file then run a slash install on it to get a Windows Service of the Raven DB running.

Raven DB Installation results (click for full size image)

Raven DB Installation results (click for full size image)

To verify that it is up and running (which if you’ve gotten these results, you can rest assured it is, but I always like to just see the services icon) check out the services MMC.

Launching services (Click for full size image)

Launching services (Click for full size image)

There it is running…

Now, you’re not complete yet. There are a few other things you may want to take note of to be sure you’re up and running in every way you need to be.

The management and http transport for Raven DB is done on port 8080. So you’ll have to open that port if you want to connect to the services of the database externally. On windows, open up the Windows Firewall. Right click on the Inbound Rules and click Add Rule.

Select Port (Click for full size image)

Select Port (Click for full size image)

Select the Raven.Server.exe (click to see full size)

Select the Raven.Server.exe (click to see full size)

Inbound Rule (Click for full size image)

Inbound Rule (Click for full size image)

Open up however needed. (Click for full size image)

Open up however needed. (Click for full size image)

Public Private etc. (Click for full size image)

Public Private etc. (Click for full size image)

Enter a name and description on the next wizard dialog screen and click on Finish.

Displayed active firewall rule (Click for full size image)

Displayed active firewall rule (Click for full size image)

Now if you navigate to the IP of the instance with port 8080 you’ll be able to load the management portal for Raven DB and verify it is running and you have remote access.

Raven DB Management Screen

Raven DB Management Screen (Click for full size image)

At this point, if you’d like more evidence of success, click on the “Create Sample Data” button and the management screen will generate some data.

Raven DB Management console with data (Click for full size image)

Raven DB Management console with data (Click for full size image)

At this point you have a live Raven DB instance up and running in Tier 3. Next step is to break out and add nodes for better data integrity, etc.

Summary

In this write up I’ve shown a short how-to on installing and getting Raven DB ready for use on Windows Server 2008 in Tier 3’s Enterprise Cloud environment. In the very near future I’ll broach the topics of big data with Raven DB, and other databases like Riak and their usage in a cloud environment like Tier 3. Thanks for reading, cheers!

PDX & SEA Code Camp, OS Bridge, OSCON, Iron Foundry, Robotech and Action! Stage II

I usually don’t post two blog entries in one day, but I had so much to rattle on about it seemed like a rule to break.

DeployCon, Cloud Expo and Cloud Bootcamp

I’ll be speaking at the Cloud Bootcamp at the Cloud Expo in New York City. So if you’re coming to the conference, swing by and let’s talk PaaS and the future of software development and cloud computing. I’m looking forward to the event, it’ll be a good time and has a lot of educational content.

Also during Cloud Expo, be sure to check out the DeployCon. The DeployCon Conference is a PaaS Conference put together by Rishidot Research. Check out more information here.

Iron Foundry

Over on the Iron Foundry Project we’re going to be putting together some new material on what’s next, where we are on the project and where we are headed. The effort will be pushing forward with some possible hackathons or installathons for those interested. So if anyone is keen on checking out the latest and greatest of .NET PaaS options available, send me an e-mail and we’ll start coordinating some efforts.

Robotech

Yeah? Do you know the designation of the fighter type?

Yeah? Do you know the designation of the fighter type?

So why am I bringing up animated Anime from the 80s? Well, I was a pretty huge fan of the series, played the RPG, and own a few of the toys. Which yes, puts me in the nerd realm all that much more.

Know what this is?

Know what this is?

For the next few months I’ve decided that we’re going with Robotech for code names of our projects. Who is “we”? I mean that in the sense that any and all projects I’m working on are going to be prototype names from Robotech. So if you notice a Robotech theme going on, that’s the reason.

Action Shots

As promised, action shots…

…the Destroids stand guard over Portland and the Zentraedi onslaught. Just my creative dorky side.

Destroids standing ready...

Destroids standing ready…

Tomahawk

Tomahawk

Cheers!

PDX & SEA Code Camp, OS Bridge, OSCON, Iron Foundry, Robotech and Action!

May has been insane. I’ve spent a total of about 3 days of the entire month where I live in Portland, OR. It’s kind of an odd feeling to try not to travel since I love it so much. But I’m going to try and take it easy  this month and next. Especially since some kick ass conferences and code camps are happening right here in Portland (and Seattle) which helps me spend some quality time right here with Stumptown (that’s a nick name for Portland btw). So here’s a run down of the crazy action happening in June and July. There are lots of events and I’ve got lots of things coming your way!

PDX & SEA Code Camps

I just wrapped up speaking at Portland Code Camp. Again, thanks for coming out and hearing about PaaS Technologies, Cloud Foundry, Tier 3, AppFog, AppHarbor, Continuous Deployment, Integration, and all the things that have been pushed forward with Platform as a Service!

At the upcoming Seattle Code Camp on June 16th I’ll be providing 3 presentation, or workshops, or sessions, or whatever you may want to call them.  Here’s a quick blurb about these, if interested, head down and I’ll make sure you get into the presentation workshop sessions. Also note the schedule, which no, I did not make the schedule so I apologize ahead of time that I will be talking about Node.js at the mind numbing early hour of 8 am.

  • Node.js Rulz! JavaScript takes over the full stack! => From the client side with some jQuery action to the back end with Node.js, with a touch of JavaScript Object Notation . JavaScript is everywhere these days and simplifying our lives. In this session I’ll run the full stack, with a live example, deployed to a live environment to show how JavaScript is freeing us from the constraints of the traditional development environment.
  • Removing the Operating System Barrier with Platform as a Service=> This session will cover the major advances of platform as a service technology, what’s available in the OSS space to enable faster, easier, higher quality software development cycles in the cloud. The session will complete with a demo of PAAS technology in use, deploying a highly scalable, distributed & dispersed web application.
  • Putting it All Together, Letting Apps Lead the Cycle, TDD In The Cloud =>  I’ll be taking a deep dive into cloud architectures and how to build applications, generally at the PaaS level mixed with a little IaaS, to get people rolling with high velocity, high quality, and without the need to worry about the little things.  Want to learn about why PaaS and cloud computing is altering the very fabric of the development cycle? Want to know how to dive in with some abstractions and behavioral practices on the cloud, using PaaS, to bring apps, prototypes, and UX to market faster than anyone else? I’ll be touching on all of these things during this long form session. The sessions will step through these core concepts and ideas.

OS Bridge

Ouch, they didn’t pick any of my sessions.  :’(  Well, even though I wasn’t selected to present I will absolutely be at OS Bridge and you should be too! So if you can get into Portland between the 26th and 29th of June make the endeavor! There will be great networking, sessions and you get an excuse to hit up Portland’s awesome Cart Selection of exquisite food (if you haven’t been here, I’m NOT kidding, it is indeed epic!). Be sure to say hello or let’s pair up on some code or hack some PaaS apps.

OSCON

I’ll be attending OSCON, probably coding all the while. I’ll be reporting on a number of things, specifically the Cloud Track:

Rid the MAX to OSCON, from downtown, or the airport, or...

Rid the MAX to OSCON, from downtown, or the airport, or…

http://www.oscon.com/oscon2012/public/schedule/topic/805. If you’re going to be attending, again, ping me and we’ll meet and maybe build something, maybe start a twitter flame war and correct everything on the web, or something of that sort. Worse case scenario we’ll grab a beer and have some rocking conversations about OSS, Cloud Tech, and more.

Part II of this blog entry is coming a little later today…  so stay tuned for Robotech, Iron Foundry and all types of code action.

#nodejs, why I’m basically porting EVERYTHING to it…

Here’s my list of why I’m moving everything to Node.js that I run (i.e. maybe even THIS wordpress blog eventually).

  • Between the enhancements Google gave to JavaScript and the ease of use in writing with the language, it provides the least resistance of any framework and language stack out there.
  • Node.js + Express.js or Bricks.js + Jade + Every DB Choice on Earth really is a convincing reason too.
  • The developer community, if it isn’t now, is ridiculously close to the biggest development community on Earth. The JavaScript community goes into every corner of development too and crosses over easily into Ruby on Rails, .NET, and Java. Nobody is left untouched by JavaScript. This provides more avenues of joining up for projects than any other platform in existence.
  • Hiring for startups, mid- or enterprise business to build node.js and Javascript apps is 10x easier than hiring for anyone else right now. Which still makes it almost impossible. But that means it is “almost impossible” vs. “impossible” as it is with the other stacks!
  • Node.js is fast enough, and easy enough to distribute and less resource intensive than almost anything on the market. All that and it requires almost nothing to configure and setup compared to Apache, IIS, and a bunch of those other solutions.
  • The PaaS Solutions out there, thanks in large part to Nodejitsu, Nodester, and even the Windows Azure Node.js team have made deploying Node.js apps the easiest stack to deploy around – hands down – no contest.
  • Node.js uses JavaScript (if you haven’t noticed) and most of the NoSQL solutions already speak the common language, JSON or BSON which makes layering more transparent in your architectures.
  • I could go on… but you get the idea.  Node.js + JavaScript makes life EASIER and gives me more time to do other things. Other stacks typically have me tweaking and tinkering (which I do find fun) for hours more at a time per project than a Node.js Project. Generally though, I like to get a beer at some point, and Node.js get me there earlier!

Sure, I’m sticking to being polyglot. I’m even headed to the Polyglot Conference in Vancouver BC this evening. But nothing is as approachable as Node.js + JavaScript. Looking forward to a lot of PaaS discussion around Node.js and getting interoperability against .NET, Java, Rails and other frameworks.

So expect to see a lot more Node.js and JavaScript bits on the blog!  🙂   Cheers!

Building a Node.js + Express.js + Jade CoderWall + Geekl.st Portfolio (cont…)

In the previous blog entry I went thru the steps needed to get a Node.js site up and running with Express.js. Next I’m going to leap right into getting some mash ups going with Coder Wall. I’m currently waiting on Geekli.st to get me some beta API access, when that happens I’ll be adding some of the geeky list to the portfolio. For now… on with the mash up.

Folder Structure

Folder Structure

First things first, get the pertinent pieces you need from proudify.js (check it out here: https://github.com/icebreaker/proudify and on Mihail’s site here: http://proudify.me). My folder structure looked like this once I had pulled in the js & css files I needed. You may notice I have three image files too, I picked them up via http://iconfinder.com, but you can snag my github and they’re included in that.

If you just want to clone the code, I do have it available on github @ https://github.com/Adron/codingwall.

. . . . Next I setup the index.jade like this:

h1= title

div.splitter
    div.left
        div.navAlpha
          p Welcome to #{title}'s Portfolio Site

          a(href='http://www.linkedin/in/adron’)
            | <img alt="Linkedin" src="images/linkedin.png" style="border: 0px" />
          br
          a(href='http://twitter.com/adron&#8217;)
            | <img alt="Twitter @adron" src="images/twitter.png" style="border: 0px" />
          br
          a(href='http://www.facebook.com/adron&#8217;)
            | <img alt="Facebook" src="images/facebook.png" style="border: 0px" />

        div.navBeta
          p #{title}'s Other Web Presence

          ul
            li
              a(href='http://compositecode.com&#8217;)
                | Composite Code
            li
              a(href='https://github.com/Adron&#8217;)
                | Github
            li
              a(href='http://www.linkedin.com/in/adron&#8217;)
                | LinkedIn
            li
              a(href='http://www.facebook.com/adron&#8217;)
                | Facebook
            li
              a(href='http://twitter.com/adron&#8217;)
                | Twitter

    div.right
        div.crazy
          p the content

After I setup the index.jade I changed the layout.jade to have the following code.

doctype 5
html(lang="en")
  head
    title= title
    link(rel='stylesheet', href='/stylesheets/style.css')
    link(rel='stylesheet', href='/stylesheets/site.css')
    link(rel='stylesheet', href='/stylesheets/splitter.css')
    link(rel='stylesheet', href='/stylesheets/proudify.min.css')
    script(src='/javascripts/jquery-1.4.4.min.js')
    script(src='/javascripts/jquery-ui-1.8.7.custom.min.js')
    script(src='/javascripts/jquery-proudify.min.js')
  body!= body

Those are basically all the changes I made for the first push to github. Run the standard app:

node app.js

Once it runs you should see the basic display of information. The proudify.js pulls the CoderWall badges from the their site.

Coding Wall

Coding Wall

At this time I still haven’t had time to weave in the Geekli.st yet, but will work toward doing that in the future and making a post.

I’ll be adding other features to this, as an example, around database support, connecting to services and a host of other functionalities. So stay tuned to this blog and be sure to follow the github repository for the latest bits.

Until then, enjoy.