A look at new technologies Microsoft is embracing in the Azure and .NET platforms, including JSON, JavaScript, Node.js, MongoDB and AMQP.

1. E LT O N S T O N E M A N , U K C S U G : A P R I L 2 0 1 3
NON-MICROSOFT
TECHNOLOGIES
MICROSOFT IS EMBRACING

2. AGENDA
• JSON
• JavaScript
• NoSQL
• Node.js
• AMQP

3. JSON
• Serialization format
• “JavaScript Object Notation”
• Concise, human-readable, interoperable
• No schema
XML
<vehicle
xmlns=“http://schemas.xyz.com/vehicles”>
<makeCode>audi</makeCode>
<modelCode>a3</modelCode>
</vehicle>
JSON
{
"modelCode":
"a3",
"makeCode":
"audi"

4. JSON: WHY SHOULD I CARE?
• Performance
• Interop (json.org)
• Ease of access
• Modernity

5. MICROSOFT AND JSON
• Available in WCF from Fx 3.5
• DataContractJsonSerializer
• WebHttpBinding
• First-class option in ASP.NET Web API
• MVC 4 & Fx 4.5
• 3rd party JSON.NET library

6. JSON IN .NET
• WCF Demo

7. JSON IN .NET
• WCF Demo – Recap
• Explicit in service definition
• [WebGet(UriTemplate="makes", ResponseFormat=
WebMessageFormat.Json)]
• Hard to customise

8. JSON IN .NET
• ASP.NET WebApi Demo

9. JSON IN .NET
• ASP.NET WebApi Demo - Recap
• Implicitly available, by client request
• Accept: application/json
• Easily customisable

10. JAVASCRIPT
• Weakly-typed OO language
• Interpreted, browser runtime
• Event loop & callback mechanism
window.setInterval(function() {
document.getElementById("container").innerHTML+='<p>More</
p>';}, 500);
function writeMore() {
document.getElementById("container").innerHTML+='<p>More</
p>';
}
window.setInterval(writeMore, 500);
JsFiddle
JsFiddle

11. JAVASCRIPT: WHY SHOULD I CARE?
• Rapid development/prototyping
• Widen API reach
• Single codebase for JS runtimes
• Web apps and mobile apps
• Inherently async
• Server-side applications

12. MICROSOFT AND JAVASCRIPT
• jQuery in ASP.NET + IntelliSense
• Knockout (MVVM), modernizr (HTML5)
• TypeScript
• Superset of JavaScript, adds type-safety, class &
interface definition
• Compiler generates pure JS
• Eases learning curve from .NET
• VS plugin (and Vim, Emacs) + WebEssentials
• Pre-dates ECMAScript 6

13. JAVASCRIPT
• TypeScript Demo

14. FROM TYPESCRIPT
module ApiClient {
export class Vehicles {
getModels(makeCode: string) {
return 'someJSON';
};
static baseUrl =
'http://localhost/Sixeyed.CarValet.Services/VehicleService.
svc';
}
}
var client: ApiClient.Vehicles = new ApiClient.Vehicles;
var models = client.getModels('rover');
• TypeScript Demo - Recap

15. TO JAVASCRIPT
var ApiClient;
(function (ApiClient) {
var Vehicles = (function () {
function Vehicles() { }
Vehicles.prototype.getModels = function (makeCode)
{
return 'someJSON';
};
Vehicles.baseUrl =
'http://localhost/Sixeyed.CarValet.Services/VehicleService.
svc';
return Vehicles;
})();
ApiClient.Vehicles = Vehicles;
})(ApiClient || (ApiClient = {}));
var client = new ApiClient.Vehicles();
var models = client.getModels('rover');
JsFiddle

16. NOSQL
• “Not-only SQL” -> document databases
• No schema, collections of objects
• Mature products
• Rich, efficient querying (+LINQ)
• Indexing
• Map/reduce

17. NOSQL: WHY SHOULD I CARE?
• Easy access, REST+JSON
• Cloud integration – Shared Database
• Accelerated delivery
• Fewer moving parts
• Simpler solution
• Simpler maintenance
• Performance & scale-out

18. MICROSOFT AND NOSQL
• SQL Azure beta -> Table Storage
• NoSQL, with limitations
• MongoLabs Azure Add-On
• MongoDB hosted on Azure

19. NOSQL
• MongoDB Demo

20. NOSQL
• MongoDB Demo – Recap
• Azure Add-On, NuGet driver
• GetServer().GetDatabase().GetCollection<>()
• LINQ
• Wrapper class
• BSON ObjectId

21. NODE.JS
• JavaScript platform
• Built on Google’s JS runtime
• Server
• Websites
• Accelerators
• Gateways

22. NODE.JS: WHY SHOULD I CARE?
• Single-threaded, non-blocking, async
• Efficient & scalable
• Large, dedicated community
• Rich package management (NPM)
• Leading-edge – Socket.io, MongoDB

23. MICROSOFT AND NODE.JS
• IISNode
• IIS Express, Node.js extension for IIS7
• Node.js on Azure

24. NODE.JS
• FormatService Demo

25. NODE.JS
• FormatService Demo – Recap
• Simple HTTP server
• Require modules (internal/external)
• JS async model – passing callbacks
• Hosted on Azure websites
• Git publishing
• Platform agnostic

26. AMQP
• Advanced Messaging Queuing Protocol
• Interopable, standards-based wire protocol
• Fast, durable, scalable
• History & heavy usage in finance industry
• Industry adopters
• RabbitMQ - VMWare
• Apache Qpid
• Windows Azure Service Bus

27. AMQP: WHY SHOULD I CARE?
• Rich functionality & messaging patterns
• Interoperable MQ standard
• Ignore protocol, focus on message
• Multiple providers
• Choose your cloud (StormMQ…)
• BUT
• Few full AMQP providers
• And notable missing parties (SQS, ZeroMQ)
• How interoperable?
• Traction?

28. MICROSOFT AND AMQP
• v1.0 launch (2011)
• AMQP support for Azure Service Bus
• Queue, topic, subscription
• Limited client support…

29. AMQP
• Node.js + RabbitMQ Demo

30. AMQP
• Node.js + RabbitMQ Demo Recap
• 3rd party AMQP module
• Built for RabbitMQ
• RabbitMQ .NET client library
• Durable messaging
• Multiple consumers

31. AMQP
• Node.js + Service Bus Queues Demo

32. AMQP
• Node.js + Service Bus Queues Demo – Recap
• Azure Node.js module
• AMQP module doesn’t connect to Azure
• Azure .NET Client Library
• RabbitMQ client library doesn’t connect to Azure

33. CONTACT
• elton@sixeyed.com
• http://geekswithblogs.net/eltonstoneman