API Icon

API

An API (Application Programming Interface) is a collection of protocols and subroutines for building software.
18 Stories
All Topics

Ballerina blog.ballerina.io

Ballerina goes 1.0

You may have initially heard of Ballerina on episode #313 of The Changelog. Well, the “first cloud native programming language” has finally reached its milestone 1.0 release! After more than 3 years of hard work by an incredible team, I am thrilled to announce the general availability of Ballerina 1.0! Congrats to Paul and the team for powering through and shipping something they can be proud of! Check the announcement post for all the details of what “1.0” means for Ballerina.

read more

Manuel Vila github.com

Deepr – an alternative to GraphQL?

Manuel Vila: What makes GraphQL so exciting is the ability to compose method calls, and Deepr is a way to achieve that and only that. Because everything else, we believe, would be better implemented somewhere else in the stack. Deepr is being built by folks who’ve been using GraphQL for awhile, love it, and have some ideas about how things might be even better by changing some key decisions. Worth a look, for sure.

read more

The Changelog The Changelog #313

The first cloud native programming language

Jerod talked with Paul Fremantle, the CTO and Co-Founder of WSO2, about their new programming language, Ballerina — a cloud-native language which aims to make it easier to write microservices that integrate APIs. They talked about the creation of the language and how it was inspired by so many technologies, cloud native features like built-in container support, serverless-friendly, observability, and how it works with, or without, a service mesh — just to name a few.

read more

Sarah Perez TechCrunch

Is Twitter breaking Twitter?

Twitter is at it again making controversial changes restricting how the developer community can use their APIs to develop 3rd party Twitter clients. Sarah Perez reports on TechCrunch: Twitter is breaking users’ favorite third-party Twitter clients like Tweetbot and Twitterific by shutting off APIs these apps relied on. Worse still, is that Twitter isn’t taking full responsibility for its decisions. In a company email it shared today, Twitter cited “technical and business constraints” that it can no longer ignore as being the reason behind the APIs’ shutdown. This change sparked the #BreakingMyTwitter hashtag

read more

John Resig blog.graphql.guide

Introducing the GraphQL Guide

John Resig and team at Khan Academy implemented a generic GraphQL platform and their development practices changed overnight. The benefits they saw were so substantial that he and Loren Sands-Ramshaw decided to write a book about it. …we’re using GraphQL in more and more places: we are transitioning older pages over to use GraphQL and have a mandate in place that all new pages need to use GraphQL. The benefits that we’ve reaped have been so substantial, even though it’s still early days. We’re writing new products faster, we’re able to rapidly iterate on designs, and we’re keeping our server implementation slim. Wow, “REST APIs now feel quite antiquated…” I look at how well it’s worked for us and read stories about how GraphQL has changed other organizations, and I can only think that GraphQL is going to dramatically change how we all build APIs going forward. REST APIs now feel quite antiquated by comparison. Beta chapters of The GraphQL Guide are available now.

read more

Diego Bernardes github.com

Flare – a service that notifies of HTTP endpoint changes

Flare listens to changes on HTTP endpoints and notify subscripted clients about the changes. It help reduce the pressure on APIs by avoiding the clients to do pooling requests to search for new/changed content and the need of the APIs to develop workers to notify the clients about the. Pitched as useful for microservice architectures, but could find lots of uses outside of that context too.

read more

Chris Manson blog.stonecircle.io

The true power of JSON API – have someone else do it

This is an excellent post with some immediately useful takeaways (and some open source, to boot). Chris starts it with a compelling description of JSON API’s value proposition: how to use JSON API as an “anti-bikeshedding weapon” Building Restful APIs requires hundreds of tiny decisions, which is like having a bike shed on every corner. Outsource the little stuff!

read more

0:00 / 0:00