The last few years, RightScale has been surveying organizations and putting together the annual “State of the Cloud Report”. The survey includes data collected from 997 technical professionals across a broad cross-section of organizations, and focuses on gathering information about their adoption of the Cloud. Some of the metric included in the report show the…
Thomson Reuters has released their first Top 100 Global Technology Leaders list to define new criteria for determining leadership in the 21st century. They’ve already been tracking tons of metrics on companies all around the world for their clients, and have decided to combine it all to create this new list. Thomson Reuters feels they’ve…
Did you know you can download a specific set of docs as a PDF without it taking gigabytes of space, enabling you to take it anywhere with you on your desktop or mobile device.
Simply go to the particular docs you’re interested in, for example the Azure Application Architecture Guide and then below table of contents on the left side you will see a Download PDF button.
Clicking the Download PDF button will open up the latest version of the docs for this topic in a browser and from here you can click to save.
As you can see it downloaded a 73 page PDF document with all the content found online.
As content is changed online, clicking the Download PDF will result in getting the latest version of this document.
To follow up and learn about other updates to the Microsoft Docs site, follow their blog at https://docs.microsoft.com/en-us/teamblog/.
A lot of workloads are driven by peak consumption. From my experience, there aren’t the amount of workloads that have a constant performance need are in the minority. Now here comes the interesting opportunity when leveraging serverless architectures… Here you only pay for your actual consumption. So if you tweak your architecture to leverage this, then you can get huge gains!
For today’s post, I’ll be using VMchooser once again as an example. A lot has changed since the last post on the anatomy of this application. Here is an updated drawing of the high level architecture ;
Underneath you can see the flow that’ll be used when doing a “Bulk Mapping” (aka “CSV Upload”). The webapp (“frontend”) will store the CSV as a blob on the storage account. Once a new blob arrives, a function will be triggered that will examine the CSV file and put every entry…
View original post 953 more words
If you’ve been using Git from within Visual Studio 2017 you might be aware of the fact that when performing a fetch it would not automatically prune your local list of branches that no longer exist on the server. Typically you would have to open up a Command Prompt and run the following command to cleanup your list of branches that exist on the remote:
> git remote prune origin
Well now with Visual Studio 2017 Update 5 you can now configure your global and repository settings to prune your local list of branches on every fetch. Let’s take a look at how you can configure this.
First download and install Visual Studio 2017 Update 5. You can do this from within Visual Studio under the Tools menu:
Once you have Visual Studio 2017 Update 5 installed, go to the Team Explorer pane and click on Settings where you can configure your default behavior for your Global and/or Repository Settings:
Now you can change the setting to prune remote branches on every fetch. In my opinion this should be the default value.
Another nice addition to the Git settings in Visual Studio 2017 Update 5 is the ability to Rebase your changes when you pull. I’ll explore that in a future post.
In summary when enabling the prune on every fetch, this means your local list of branches is always up-to-date with the remote. Pruning will cleanup and remove your local tracking branches that no longer exist on the server.
Recently, I’ve created an audition video to become a Pluralsight author. I wanted to share this video, as it might be interesting for you. The video gives an introduction to Azure Logic Apps and finishes with a great demo about Saleforce integration (at 5:43).