InfoQ Homepage API Content on InfoQ

Articles

RSS Feed

Newer Older

Development

How Zalando Delivers APIs with Radical Agility

InfoQ interviewed Thomas Fraustein, architect at Zalando, about his team’s radical agility development organization that is optimized for an API-first approach. He explains what an API-first approach is, and provides tips on building good APIs for scalable microservice architectures where a large number of services are offered efficiently.

Jerome Louvel
on Dec 24, 2016
Development

Virtual Panel: Document and Description Formats for Web APIs

In this virtual panel we hear from 4 individuals deeply involved in the Web API space. Each of them has a unique take on the values, benefits, and costs of documentation and description formats in general, and provide their own unique perspective from their vantage points across the Web. They agree on one thing: something must be done to help developers find their way through the world of Web APIs

Benjamin Young
on Oct 14, 2016
Development

An Open API Initiative Update

The Open API Initiative group is evolving what has become the de-facto standard API Description Format to produce a consistent and compatible format for describing APIs, allowing interoperation between tooling, systems, and runtime environments. Tony Tam, creator of the popular Swagger Specification is providing an update on the group activity.

Deepak Nadig
on Sep 30, 2016
.NET

On Abstractions and For-Each Performance in C#

Donald Knuth famously said, “We should forget about small efficiencies, say about 97% of the time”. But when faced with the other 3%, it is good to know what’s going on behind the scenes. So in this article we’ll be taking a dive into the foreach loop.

Jonathan Allen
on Sep 29, 2016
.NET

Designing with Exceptions in .NET

Exceptions are an integral part of working with .NET, but far too many developers don’t think about them from an API design perspective. Most of their work begins and ends with knowing which exceptions they need to catch and which should be allowed to hit the global logger. You can significantly reduce the time it takes to correct bugs if you design the API to use exceptions correctly.

Jonathan Allen
on Sep 09, 2016
.NET

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.

Amel Musić
on Aug 19, 2016
Java

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.

Greg Brown
on Jul 12, 2016
.NET

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.

Jonathan Allen
on Apr 04, 2016
Mobile

Enterprise Mobility is Going Beyond “Mobile First” Approach. Are You Ready?

The mobile revolution is changing the way organizations work and manage their operations, as well as engage with their employees. As a result, organizations are reconsidering their technologies and techniques to make their traditional organizational cultures and roles more mobile friendly, making ‘mobile first’ a must have strategy.

Jaykishan Panchal
on Mar 31, 2016
Architecture & Design

Microservices Evolution at SoundCloud

At the MicroXchg conference in Berlin, Bora Tunca from SoundCloud presented the evolution of SoundCloud’s microservices architecture throughout the years. We had the opportunity to interview him and learn more about SoundCloud’s architecture evolution and microservices in general.

Alex Giamas
on Mar 21, 2016
Architecture & Design

One API, Many Facades?

An interesting trend is emerging in the world of Web APIs, with various engineers and companies advocating for dedicated APIs for each consumer with particular needs. Beyond any ideal design of your API, reality strikes back with the concrete and differing concerns of varied API consumers. You might need to optimize your API accordingly.

Guillaume LaForge
on Mar 13, 2016
Development

Graph API in a Large Scale Environment

MyHeritage is a rapidly-growing destination used around the world to discover, preserve and share family histories. There is increasing demand for our services, accessed both internally and externally by our partners via the FamilyGraph API. Millions of API calls are made every day providing a huge challenge in terms of performance, scalability and security.

Maor Cohen
on Feb 13, 2016

Newer Articles

Older Articles

InfoQ Software Architects' Newsletter

Articles