I saw a LEAN webcast last year and learned about something creating a Steel Thread that can emulate what you want to application to do without any business logic. This is a “throw your code away” exercise, so there’s no pressure, right? Well sort of. At this point we know very little about the problem, and less about how the solution will look.
The idea here is to use what you do know based on customer interviews, and their ideas for success and turn that into something you can deploy in a day or two, but works. Again, we’re not going to re-use any of this code since when we finish it will effectively be a hot mess of coupled and brittle code we wouldn’t want to keep around anyway, maybe we can call it an ‘ugly spike’.
Steel Threading supports the notion that you can start at point “A” and traverse 4, 8, 9, or (n) other points arriving at the destination in the state you expected – think “Chutes and Ladders”; you may or may not make it from one point to the next, but you’re learning as you go.
The ultimate goal is to work inside the box and not prescribe something for the solution that doesn’t work or they can’t sustain. It is a spike of sorts, but it helps kick off the project in a direction that makes sense today, tomorrow or next week might be totally different – we’ll worry about next week, next week.
The Initial Stories
I have 15 stories with high-to-medium level detail to start with. This isn’t going to be an Amazon or Zappos, but it will be something ecommerce in nature. Since most of the common scenarios have been solved by the industry we can take some fairly intelligent hints on how we like things to happen. For example, don’t put a product in my shopping cart – and let me pay for it, if it’s been discontinued. That said, I can focus on executing on my customers goals for this solution.
Where Azure Comes In
All that said, I’ve got an MVC web role, and a worker role in my (disposable) steel thread solution. I can add more projects to the solution while I’m finishing this exercise if I need to, but this is the starting point right now.
Our local Orlando user group hosted Scott Densmore from the Microsoft PnP Team who discussed taking a stock ASP.NET project and wiring it to AppFabric’s Access Control services. That’s what I need to do to support a few of my stories I’ve collected so far.
The web role will submit stuff that needs to be picked up and persisted, so I’m thinking about using a queue to intercept these submissions, then move the submission into table storage. There’s already guidance around this in a few places so it should wire up quickly and work. The content types I’m concerned with have different rules on submission, so there may be a bit of a workflow involved with the submission that might it a bit prickly.
I’m going to run most of this from my local DevFabric, I’m not sure there’s a need to deploy it except for the fact of getting good/better at deployments. Besides, deployment looks a bit involved to me at the moment, so getting a few deployments behind me will only help.
On a side note, I was a bit jealous this morning reading about a VS2010 plug-in for Rackspace deployments – very cool stuff. The case study was written up by Microsoft so I would only think they are working out the same types of features to keep us out of their management portal and inside the IDE – maybe a new project property tab based on the type of project template? That would be cool.
Here are my two development environments:
– Both work and home are running the 64-bit Windows 7 Awesome SKU
– Both work and home have at least 4Gb of RAM (work has more)
– Both work and home have at least 2 cores (work has many more)
– Both are running SQL Server 2008 R2
– Azure 1.3 Toolkit
– VS2010 SP1
– GitHub for SCM, for now anyway
That’s it for now.