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.
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.
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.
MyHeritage and its FamilyGraph API support millions of API calls every day providing a huge challenge in terms of performance, scalability and security.
Bulk data is usually accessed via files & FTP. As collaboration migrates to APIs, what are the requirements for data APIs? Here we describe a meta-data driven architecture for bulk data ingestion.
Mike Amundsen's series "Designing APIs for the Web" is a straightforward dive into API design suitable for a broad set of stakeholders. This article reviews the series so you know what to expect.
Many Web API designers claim their are RESTful, but their APIs have little in common with REST. What can be done to make a web service API truly RESTful? 8
Val Huber explains creating a RESTful API from an existing database schema, extending the API to define multi-table hierarchical resources, and adding behavior using declarative reactive expressions. 2
The RAML API specification language includes constructs that reduce duplication inherent in other formats. This article steps through a simple API design to illustrate some of RAML's DRY features. 1
As mobility is transforming our lives, this article gives a step-by-step approach on how enterprises can seamlessly connect their mobile workforce to back-end systems for increased productivity. 1
Reza Shafii explains how to satisfy two fundamental needs of API design and implementation, as defined by the API hierarchy of needs, with RAML, API Designer and APIkit.
We demonstrate how to build a RESTful API on top of CQRS systems. The result joins HTTP semantics and REST style with distributed computing concerns such as eventual consistency and concurrency. 7