CosmosDb is the "planet scale" document storage (I love that term) schema-less (NoSQL) system that is offered by Microsoft Azure. It offers guaranteed performance based on how much throughput you select when provisioning it. This is measured using "Request Units" (RU's). It aims to offer virtually unlimited scalability and throughput through the use of partitioned collections spread across a series of high performance storage hardware (SSD's).
Many times when speaking with colleagues and friends I get asked "What should I concentrate on from a tech perspective?". This may be to plan some professional development, or to try and steer your career into where you want it go, or simply to provide some guidance around the myriad of things to look at in the tech world. I like to do this for both personal and career goals, but for this post I'll stick to tech. The technology landscape is huge and it can be hard to focus when there are so may things that are interesting. You do not want to spread yourself "too thin" either, and tackle too many things otherwise you will either never get to it or it will seem overwhelming.
Microsoft Azure API Management is a cloud hosted service provided by Microsoft to easily manage your API (Application programming interface) solutions. Azure API management allows you to easily secure, measure, configure and provision multiple API solutions at scale, to any downstream API you create.
We live in very exciting times. Computing capabilities have increased exponentially in the last two centuries to allow us to easily utilise highly complex artificial intelligence functionality today. It all began with the first mechanical computer in the early 19th century by Charles Babbage. The concepts and work that resulted from that were iterated upon, which enabled the invention of the first programmable digital computer in the 1940s. Fast forward 70 years, and Artificial Intelligence is evolving into something that people can easily use, without having a degree in mathematics, access to enormous amounts of processing hardware or access to enormous amount of data.
App Service authentication is a feature in Microsoft Azure that allows extremely easy setup of authentication using either:
This post is about some of the issues I had installing the latest docker toolbox and how I went about solving them to be able to finally get docker working on my windows system.
For those not familiar with docker and what it is/does, I suggest going here and reading up on it a bit.
For the record, I have a fairly standard Windows 10 laptop, which was upgraded from Windows 8.1. Gigabyte P34v2 with 16Gb of memory and a 256Gb SSD. Nothing special.
Twitter kindly informed me of a great blog post by Scott Hanselman around "Brainstorming development workflows with Docker, Kitematic, VirtualBox, Azure, ASP.NET, and Visual Studio" so I decided to follow the steps and give it a shot.
I started following the steps involved, although I initially missed the part about disabling Hyper-V. So disable Hyper-V and then reboot. If you are doing Cordova/Ionic development and using some of the emulators accompanying visual studio that require Hyper-V, this may be somewhat inconvenient for you.
Everything seemed to initially install fine. Docker installed all of its components including VirtualBox.
Next step is to double click the 'Docker Quickstart terminal' to ensure everything is installed as expected.
Problem 1: Docker virtual machine will not start.
Docker terminal starts up and begins setting up the environment (creating SSH keys etc), creating the virtual machine within VirtualBox and starting that machine. However, the virtual machine simply would not start and the docker terminal reported the error and stopped.
I loaded up KiteMatic which is the other utility application that the Docker toolbox installs to see if that could help. It has an option to delete and re-create the VM. So I went and did that, but to no avail. The VM gets deleted, recreated but will not start.
I tried uninstalling and re-installing the docker toolbox, realised the VM remains in VirtualBox, so deleted that VM manually (it was named ‘default’), then un-installed and re-installed again but unfortunately no go.
I loaded VirtualBox and tried to start the machine manually but no go. A dialog was shown with a 'Details' button which revealed the following error:
Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter' (VERR_INTNET_FLT_IF_NOT_FOUND).
Hmm, not that informative but plonking the error code into google/bing revealed many posts of others having similar issues.
My 'Glav.CacheAdapter' package has recently had a major release and is now at version 4.0. If you are not familiar with what this package does, you can look at previous posts on the subject here and here. In a nutshell, you can program against a cache interface, and via configuration, switch between ASP.Net web cache, memory cache, Windows Azure Appfabric, memcached and now redis.