Subscribe! (MP4) - Channel 9
Summary: Subscribe! is a video blog about Messaging, Middleware, Architecture, and all sort of other interesting topics around building larger and more sophisticated solutions than your average website on Windows Azure and Windows Server. Your host and, mostly, monologist is Clemens Vasters from the Windows Azure Service Bus team who puts this blog together in his studio on his island of solitude in Germany. Follow Clemens on Twitter @clemensv
This is the last (numbered) episode in this series and I'm showing you the code that runs on the Pi in my car as well as the server side code that pumps the data into storage. Mind that the code is built for demo/explanation purposes, so it's not as robust as production code would be and it's missing retry and failure detection logic. GitHub repo https://github.com/clemensv/D2C-RPi-OBDLogger Startup Script: https://gist.github.com/clemensv/7928218 Qpid Proton: http://qpid.apache.org/index.html (GitHub https://github.com/apache/qpid-proton)OBDGPSLogger Original http://icculus.org/obdgpslogger/ See you next year with a new set of episode and have great holidays!
"Internet of Things" ist dieser Tage eines der vieldiskutierten Schlagworte in der Softwareindustrie. Bei "IoT" oder auch Maschine-zu-Maschine Kommunikation (M2M) dreht es sich allgemein um die direkte und indirekte Verbindung von zweckgebundenen Geräten wie Waschautomaten, Geschirrspülern, Toastern, oder auch Lokomotiven, LKWs und Werkzeugmaschinen an das Internet. Wir, Microsoft, sind in den vergangenen Monaten von einer steigenden Anzahl von Kunden in diesem Bereich zu Rate gezogen worden. Diese Kunden aus der fertigenden Industrie kommen zu uns mit einem oft langjährigen Erfahrungsschatz in der Automation und Sammlung von Telemetriedaten zu ihren Produkten, sehen sich allerdings vor beträchtlichen Problemen, mehrere zehntausend oder auch Millionen von Geräten gleichzeitig an einem föderierten System zu betreiben, bidirektionale Kommunikation herzustellen, und die Informationsflut zu beherrschen.. Diese Episode hier auf "Subscribe!" ist die deutschsprachige Version der ersten Episode zu diesem Themenbereich, und dreht sich um IoT/M2M im Allgemeinen, die Kommunikationspatterns, und um die Verbindungsoptionen und -problem wobei ich spezifisch auch auf VPN und die damit verbundenen, aber leider nicht offensichtlichen Probleme eingehe. Mehr zum Thema [Englisch]: June 2012 MSDN Magazine "Using Service Bus for Things" (must read) July 2012 MSDN Magazine "A Smart Thermostat on the Service Bus" Internet of Things: Is VPN a False Friend? AMQP Support in Windows Azure Service Bus
"Internet of Things" is one of the hot catchphrases of the industry these days. It's about connecting special-purpose devices (laundry machines, dishwashers, toasters, locomotives, trucks, factory robots, etc.) directly or indirectly to the Internet. As things go, several commercial customers have nudged us in the direction of taking a good, long look at this space and we're already actively helping several of them to deal with the particular scale challenges of needing to connect tens of thousands or more devices concurrently and with bi-directional information exchange. This is the first in a series of episodes I'll do on the IoT/M2M subject area here on "Subscribe!" and in this first one, I'm introducing the problem space, talk about patterns, and am talking about the connectivity options and challenges around devices, specifically also discussing VPN. More on the subject: June 2012 MSDN Magazine "Using Service Bus for Things" (must read) July 2012 MSDN Magazine "A Smart Thermostat on the Service Bus" Internet of Things: Is VPN a False Friend?
Glenn Block and crew have been working on making Node.js' real-time eventing Socket.io library scale across nodes (machines) with the help of Service Bus. Talking to and hearing Glenn talk is always fun, so I hope you'll enjoy this.
In this episode, our identity wizard Vittorio Bertocci (you can identify true wizards by the long hair, even though most other wizards carry that hair under the chin) explains Windows Azure Active Directory and its role in the Windows Azure platform.
As just announced by Scott Guthrie, we're releasing the AMQP 1.0 support for Windows Azure Service Bus today, with commercial support and full SLA. That's more than reason enough for me to sit down with David Ingham, co-editor of the AMQP 1.0 specification and my peer in the Service Bus Program Management team, and talk about the strategic relevance that AMQP has for Service Bus going forward, and how it will enable better and more heterogenous cloud solutions. More resources: Windows Azure Service Bus Latest Service Bus .NET client library on NuGet AMQP 1.0 support in Windows Azure Service Bus How to use AMQP 1.0 with the Service Bus .NET API Service Bus AMQP 1.0 Developer's Guide Apache Qpid AMQP 1.0 JMS library Apache Qpid Proton (Linux only; Windows coming soon)
If you'll want to spend some 15 minutes of your time with me,. here's the gist of the new features in the Windows Azure Service Bus .NET SDK "2.0" that we're releasing today. You can get the bits either inlined into the new Windows Azure SDK via the Web Platform Installer or, singly, via NuGet using the keyword "WindowsAzure.ServuiceBus" or http://nuget.org/packages/WindowsAzure.ServiceBus/
In this episode Rajat and I discuss about Service Bus Resource Provider REST apis which provide users programmatic way of creating service bus namespaces and managing a bunch of service bus artifacts. We also talk about the service bus analytics (Metric apis), the data that forms the basis of graphs in the new Azure Portal. With these apis you can do pretty much everything that is available on Azure Portal programmatically in a secure and consistent manner
In this episode, Ziv and myself discuss and Ziv shows us how to install Service Bus 1.0 for Windows Server, which is free (well, technical part of your Windows Server license) and can be downloaded from here.
In this episode I'm joined by our Service Bus Security and Relay PM Santosh Chandwani. We discuss the Service Bus security model including the security boundaries we have in the system and how end-to-end authentication/authorization differ from the authorization gate at the Service Bus edge. We talk about authentication and authorization options and token flow, Santosh explains the new shared-access key model in Service Bus, and how Authorization rules play a role there. The motioned SbAzTool sample is here and you can find more about the ACS integration in the docs. The shared access key documentation is forthcoming.
In this episode, Ruppert Koch and I discuss high availability options along the lines of a few samples Ruppert has written for the MSDN Code Gallery: Geo-replication with Service Bus Brokered Messages Geo-replication with Service Bus Relayed Messages Service Bus Durable Message Sender
As he'll tell you in this interview, Barry Dorrans (aka @blowdart) had a bit of an epiphany preparing for this recording in that his job is somewhat like that of infamous "Clippy". Whenever someone starts a new project, Barry and his coworkers pop up and ask whether they can help with security and "no" is never the right answer. The mandatory participation in the secure development lifecycle is all part of Microsoft's ongoing, decade-old trustworthy computing initiative, which has resulted in Microsoft's software and services to embody security best practices. More information about out secure development lifecycle can be found at http://microsoft.com/sdl Barry and I sat down to discuss the SDL, but also touch on 0-day vulnerabilities and their handling, and like anyone involved in security he has some interesting war stories to share and also some insights from recent security conferences that seem worth paying more attention to and if it's only to learn about the creativity with which people get through closed doors.
[As an exception, this Subscribe! episode is all in German. For those of you who don't understand German - this is about working in Redmond, and Ruppert and I are specifically addressing the German/Austrian/Swiss audience and particular differences in how things work in the U.S. Of course all of you can head to http://careers.microsoft.com and check out the positions we have open, including on Windows Azure.] In dieser Subscribe! Episode, die ganz ausnahmsweise mal auf Deutsch ist, sprechen Kollege Ruppert Koch und ich übers Arbeiten in Redmond und das Bewerbungs- und Auswahlverfahren für Kandidaten wie es in unserem unmittelbaren Umfeld praktiziert wird. Wir erläutern auch, welche Starthilfen Microsoft den neuen Kollegen an die Hand gibt. Wenn es Euch interessiert, vielleicht für einige Jahre oder länger im Microsoft Hauptquartier in den USA an neuen Technologien mitzuarbeiten, schaut Euch das Video an und geht dann auf http://careers.microsoft.com um Euch nach passenden Stellen für Eure Qualifikationen und Interessen umzusehen, und dann einfach mal eine Bewerbung vorzubereiten und abzusenden. Bewerbungen werden vertraulich behandelt, also gibt's nichts zu verlieren
One of the most fabulous aspects of running your apps on top of Platform-as-a-Service components is that someone else is running and watching these components for you. That doesn't let you off the hook from watching you app, but saves you from a lot of depth troubleshooting that you'd otherwise have to deal with if, for instance, you were running middleware like a messaging system yourself. For this episode I sat down with my colleague Mohamed F. Ahmed, who organizes, amongst other important things, our servicing strategy. We talk about how we proactively monitor our own systems and the other platform features we depend on, and how we actively observe logs to catch reliability issues and address privacy concerns as we do that. Mohamed and I also discuss the layered structure of our world-wide 24h/365d servicing team, with a 1st level live-site operations crew with a constantly refined operations handbook for known behaviors, backed up by on-call product team crews who investigate, if needed at 3 in the morning, and either fix issues, guide customers to solutions, or provide new procedures for the operations handbook. We talk about the various issue classifications, including the ones that will or would lead us to giving up on an entire cluster or even datacenter facility and fail over to a different one, and how we're structurally set up to learn from past mistakes and to improve our processes, which includes weekly reviews with executive leadership. If you run a service yourself, in Windows Azure or elsewhere, you may want to make some time to watch this.
Last week in Redmond I had a chat with coworker Josh Twist from our joint Azure Mobile team (owning Service Bus and Mobile Services) about the relevance of Mobile Services for organizations and businesses. As the app stores grow, there's increasing competitive pressure on organizations of all sizes to increase the direct consumer engagement through apps on mobile devices and tablets, and doing so is often quite a bit of a scalability leap from hundreds or thousands of concurrent internal clients to millions of direct consumer clients. Mobile Services is there to help and can, also in conjunction with Service Bus and other services form Microsoft and partners, act as a new kind of gateway to enterprise data and compute assets.