Now that I have upgraded my main work laptop to Windows 10, I want to learn all about the Windows 10 Universal Apps platform. I am at the beginning of this journey, so I am a beginner here. I have been looking for lots of resources to help me out and I found this TechEd training session on youtube. I have found it useful, so I thought I would share it.
I have also found the Microsoft Virtual Academy video for Windows 10 Development on Youtube. This is a longer tutorial, but covers much more detail.
In the first article in this RabbitMQ series we looked at what message queueing is and a brief look at RabbitMQ. In this article we will look in more detail at the AMQP messaging standard that underpins RabbitMQ.
RabbitMQ is built on top of the AMQP. This is a network protocol that enables client applications to communicate with a compatible messaging system.
A message broker works by receiving messages from a client (publisher) and that broker routes the message to a receiving application (consumer).
RabbitMQ currently supports version 0-9-1 of the AMQP protocol. With the AMQP protocol, a message is published by an application to an exchange. You can think of the exchange as a mailbox. The exchange then sends the message to a queue by using different rules called bindings. This is all within the message broker.
The message broker will then deliver the message from the queue to a consumer (the consumer pulls the message) that is subscribed to the queue. When a message is published to a queue, a publisher can specify various different message attributes. Some of these attributes will be used by the message broker but the rest is completely opaque to the broker and is only used by any applications that receive the message.
In this series of articles I am going to discuss how to configure and use RabbitMQ with the .NET client libraries. In this first article let’s talk about what message queueing is and then more specifically what RabbitMQ is.
What is Message Queueing
Message queuing gives you a mechanism to allow an application to asynchronously send a message to a receiver. This means that the sender and receiver do not need to interact with the message at the same time. A message is sent to a queue where it is stored until the receiver retrieves the message.
Message queues can be inter-process where the queue resides in memory on a single server or for integrating systems across multiple servers. This can be done by using in-memory queues but it is also common to use durable queues in which the messages are persisted to disk, meaning that messages are not lost should any system or server go offline for any period of time.
Message queuing systems come in many forms—both as commercial proprietry products and as open-source products. An example of a commercial solution is IBM MQ. Examples of open-source message queuing systems include RabbitMQ, JBoss Messaging , and Apache ActiveMQ.
The release of Windows 10 has been very successful for Microsoft, but there are growing concerns from people about the level of data and telemetry that Microsoft is capturing from key logging data, usage telemetry and data about application you are running (both legitimate and pirated).
There have been many articles and tips scattered around the internet about how to limit this, but I found a useful video on Youtube that talks you through tweaking Windows 10 to limit this data capture. This includes simple and obvious tweaks to the Windows 10 settings through to deleting specific windows services, modifying group policy, tweaking the registry and updating your host file to stop Microsoft calling out to their servers.
Whether you apply all of these, or just some of them it is up to you and how bothered you are by this. If you do all of these tips then you loose things like Cortana. It’s up to you and how paranoid you are about such privacy concerns.
EDIT: If you are running Windows 10 Home edition then you will not have access to the group policy editing tool.
EDIT: I have tried all these changes out on my Surface 3 (apart from the group policy bit as I am running home edition) and everything still seems to be working OK,