Mike Diiorio

Last week, I attended an AI Ready RVA event hosted at CarMax where Kyle Johnson presented the topic - vibe coding. While I was already familiar with the topic, I was interested to see what this “trend” could mean for my day-to-day work. After Kyle provided a great overview, we had time for some hands-on work. In the 20 minutes we had left, I picked a simple concept to get me started: take my LinkedIn profile and create a single-page web resume.

I failed today. There, I said it. I am not happy about it, but I own the fact that I failed. As a subject matter expert for my company, I feel like it’s important that my peers see the full picture of the process. This setback doesn’t make me any less smart. I know a ton about cloud services and even competent technologists fail certification exams. It happens to the best of us. It is okay to fail at something.

My son recently had a birthday. Since our area is still amid a significant COVID outbreak, we decided to keep the birthday party to just the family this year. Without the prospect of celebrating with a bunch of friends, I wanted to make sure that we did something special and memorable.

Following up from the previous blog post, it is time to exercise the Azure Storage Account to check out some of the basic features.

This is the first entry in what will be an ongoing series of posts related to various components and service offerings within Microsoft Azure. The landscape of cloud computing is immense and can be overwhelming to those unfamiliar with the concepts. Through the Azure Facts series, I hope to digest smaller fragments of the overall landscape and briefly examine how they can be utilized. The first topic in the Azure Facts series will focus on Blob Storage within the Azure Storage Account.

During my evaluation of BizTalk Server 2013 and the ESB Toolkit 2.2, I ran into an issue running one of my favorite components, the ESB Management Portal. I followed the set of instructions for installing and configuring the portal which were essentially the same as the ESB Toolkit 2.1 instructions. When I tried to navigate to the home page, I received a number of errors:

Microsoft unveiled a major release of Windows Azure on Thursday, June 7 at the “Meet Windows Azure” event. Windows Azure has been out for quite some time, but some in the industry are describing this as Windows Azure 2.0. The amount of new functionality is really impressive and is the culmination of more than a year of work. If you were unable to attend, the full event was recorded which can be seen at http://www.meetwindowsazure.com/Conversations.

Picking up where we left off in the Service Bus Introduction, this post will walk through a Relayed Messaging sample in order to highlight how the AppFabric Service Bus could be utilized to build Hybrid applications. In addition to the basic sample, I will also demonstrate how to provision a BizTalk Server 2010 Receive Location on the Service Bus.

Before I publish the next post on Relayed Messaging, I thought I would take this opportunity to share some lessons learned yesterday about the AppFabric Service Bus billing.

I recently had the honor of delivering a presentation entitled ‘Build Hybrid Applications Using the Azure AppFabric Service Bus’ at the Richmond and Philly.NET Code Camps. Virtually no one in either of the sessions had any previous experience with Windows Azure or the components of the AppFabric. In this series of blog posts, I will expand upon the presentation in an effort to introduce the AppFabric and take a deeper dive into the code and practical application of the Service Bus messaging patterns.