Articles

Web APIs are not just useful when making headless sites in Drupal: large Drupal sites often hold valuable information that could also be useful outside the site's context. Media companies might want to expose historical media content, community sites could show data about their community activities, e-commerce sites tend to open an API for their affiliates and partners. While it is possible to use Drupal 7 and Drupal 8 as an API backend, a lot of functionalities that describe a mature API service do not come out of the box. In this post we will explain what key concepts you have to keep in mind when designing an API service, why they are important and how APIgee Edge can make it easier to build a full-featured API webservice in Drupal successfully.

Where does technical documentation stand with agile development methods? Watch and read about the talk Rob Woodgate (@agiledoc) did at the Write the Docs London-GDS mini conference on the practice of agile documentation.

In a talk we did at FOSDEM ‘17, Tamás Demeter-Haludka and I discuss __potential application areas of graph databases in existing open source CMSs like Drupal__.

Developer portals are important for your API's adoption and support. They are also a trust signal: a well designed and actively maintained developer portal shows that an organization is investing in its APIs. It helps convince developers that they can rely on them. In this post I’ll zoom in on the trust signals business model, partner policy, API quality, API uptime status, versioning policy, documentation and developer portal production quality.

At the API days in London, I gave a presentation about developer portals. In it I shared mental models and frameworks that I think can help improve the quality of a developer portal: I decided to write 6 dedicated blog posts about what I discussed.

SQL databases are really fast when you need all the information stored together in a record row, but they are a bad fit when you need to search for relationship patterns that are not already stored together in your database. A significant performance penalty is incurred for every additional table that needs to be joined for a query. That is why SQL databases are notoriously bad at deducting relationships from datasets. Graph databases however are really good at this task.