InfoQ Homepage Microsoft Content on InfoQ
-
Creating RESTful Services with T4 Based on Model and Interfaces
When generating RESTful services with WebAPI, a lot of boilerplate code has to be implemented. Amel Musić demonstrates how T4 and EnvDTE can be used to create a flexible code generator that dramatically reduces the amount of time and effort this takes.
-
Starcounter vs. ORM and DDD
The so-called “object-relation impedance mismatch” has long been discussed in engineering circles. Most attempts at a solution rely try to mask the issue by pulling logic into the application tier. Kostiantyn Cherniavskyi looks at these issues and shows how many of them can be solved with hybrid databases such as Starcounter.
-
F# in Numbers: A Look at the Annual F# Survey Results
In April, for the second time, fsharpWorks organized the F# community survey. Over 600 developers completed the survey in 2016 (which is 15% more than in 2015). The survey provides an insight into the brains of the F# community. In this article, I'll summarize some of the results.
-
HTTP-RPC: A Lightweight Cross-Platform REST Framework
HTTP-RPC is an open-source framework allowing developers to create and access cross-platform polyglot RESTful web services using a convenient, RPC-like metaphor, while preserving fundamental REST principles such as statelessness and uniform resource access.
-
Virtual Panel: The Current State of Integration Platform as a Service (iPaaS)
Integration Platform as a Service (iPaaS) is becoming a mainstream way of connecting mobile, SaaS, IoT, and Big Data systems. This Virtual Panel focuses on some of the current trends in iPaaS and where this model of delivering integration services is headed. InfoQ has reached out to thought leaders from MuleSoft, SnapLogic and Microsoft to participate in this dialogue.
-
C#/Web API Code Generation Patterns for the RAML User
In this article, Jonathan Allen outlines the design patterns that users of REST specification languages such as RAML, Swagger, and API Blueprint should adhere to when generating code for C# and ASP.NET Web API. This includes topics such as model validation, async support, and request cancellation.
-
Big Memory .NET Part 2 - Pile, Our Big Memory Solution for .NET
In part one, Leonid Ganeline introduced the concept of big memory and discussed why it is so hard to deal with in a .NET environment. In part two, Dmitriy Khmaladze describes their solution NFX Pile; a hybrid memory manager written in C# with 100% managed code.
-
Big Data Solutions with MS SQL ColumnStore Index
Columnar data storage can offer significant performance improvements over the way database tables are traditionally stored, but they aren’t always faster. Aleksandr Shavlyuga explores the power, and limitations of SQL Server’s ColumnStore Indexes.
-
Big Memory .NET Part 1 – The Challenges in Handling 1 Billion Resident Business Objects
This article describes the concept of Big Memory and concentrates on its applicability to managed execution models like the one used in Microsoft’s Common Language Runtime (CLR). A few different approaches are suggested to resolve GC pausing issues that arise when a managed process starts to store over a few million objects.
-
Fighting Developer Fatigue with JNBridge
Developer fatigue is the overwhelming frustration felt by developers who are under pressure to keep current with a flood of new languages, libraries, frameworks, platforms and programming models. JNBridge offers a way to help alleviate developer fatigue by allowing you to mix the libraries you know with code written in the language you are learning.
-
Interview and Book Review: BDD In Action
"BDD In Action" is a book that aims to cover the full spectrum of BDD practices from requirements through to the development of production code backed by executable specifications and automated tests.
-
Metadata-Driven Design: Designing a Flexible Engine for API Data Retrieval
Bulk data is commonly accessed via files & FTP. As the world moves toward APIs to facilitate collaboration, what are the requirements for data APIs? This article describes a meta-data driven architecture for bulk data ingestion. Two APIs operate in parallel to provide data changes as well as the data records themselves. An example demonstrates how API responses are parameterized using meta-data.