Subscribe to their newsletter to stay updated on the latest API trends and industry news.
Are microservices killing the API conversation?
APIs are a great way for business to begin understanding themselves as a technology company. But could talk of microservices delve too deep for the business side to get a handle and participate? by Mark Boyd [networkworld.com]
Why Developers Should Write
As the editor of Codeship’s blog (and several other tech publications from bygone eras), I am of the strong opinion that every developer should write. by Chris Wolfgang [blog.codeship.com]
One of the big things that I love is the idea of making documentation (when needed) more of a community effort. In the past I have been in companies that seem to always rely on “customer support” or even specialized “tech writers” to do the documentation. by Jared Wray [medium.com]
API Best Practices: Documentation
API documentation is the number one pain point for developers. Simple, complete, and up to date API documentation will make or break your API operations. If developers cannot quickly get up to speed on what resources are available, and what value an API delivers, they will move on. by Kin Lane [blog.hitchhq.com]
For those using Hugo to drive their developer portal, here is a nice Github project for you: hugo-lambda – Use AWS Lambda to run the Hugo static site generator [github.com]
Allowing For Relationships Between API Developers At The App Level
Managing developers access to an API is API management 101. Managing the relationships between developers, and allowing for multiple users associated with an API application isn’t something I have seen before. Slack just added the ability to add what they call app collaborators–“adding any existing member of your Slack team as a Collaborator, including members and Guest Accounts.” [apievangelist.com]
Are API Partners the Weakest Link?
In the cyber security world there is a concept known as a supply chain attack. Essentially, what this means is that rather than attacking home base head-on, you infiltrate it by identifying weak partners or supply routes and compromising them instead. [business2community.com]
Asynchronous APIs in Choreographed Microservices
When building microservices you have to first make a decision: How am I going to manage service-to-service communication? Most developers will answer immediately: API calls. But then, more questions come to mind: Am I going to call services directly? Doesn’t it block the caller service? Doesn’t it introduce a dependency between both services? by Francisco Méndez Vilas [nordicapis.com]
API Digest #56
This time you will read about the following matters: What does it mean to monitor a Web API? APIs: Worth getting fired over? [api2cart.com]
APIs: Worth getting fired over?
APIs play a critical role in unlocking the usefulness of data and information assets by enabling them to be combined with internal or external assets. They allow unparalleled speed and scale for mashed-up services, bringing all kinds of information, individuals, companies and organizations together for purposes limited only by imagination. by Annie Turner [tmforum.org]
Opportunity and consolidation in the API industry
The move toward the cloud and DevOps as the prevailing architecture and development workflow for digital businesses has forced those same businesses to embrace an API-centric approach to growth. [sdtimes.com]
API management leaves the nest
The role of the library is rapidly morphing into the role of the API. As services-based applications continue to become the norm inside enterprises, the next logical step is often to make them available to the outside world. by Alex Handy [sdtimes.com]
Microsoft to Replace WorkingWith API with New People API
To provide more options in searching for relevant contacts, Microsoft has decided to transition WorkingWith API users to its new People API. The People API not only provides more robust metadata than the WorkingWith API, the People API includes greater browse/search functionality and ranking system. [programmableweb.com]
A Minimum Viable Product Is Not a Product, It’s a Process
“You know that old saw about a plane flying from California to Hawaii being off course 99% of the time-but constantly correcting? The same is true of successful startups-except they may start out heading toward Alaska.” [themacro.com]
New Amazon Linux Container Image for Cloud and On-Premises Workloads
The Amazon Linux AMI is designed to provide a stable, secure, high performance execution environment for applications running on EC2. The AWS API tools are pre-installed, as is CloudInit. With limited remote access, the AMI has very respectable security profile. [aws.amazon.com]
How To Succeed at Failure with Microservices
Moving from a monolith to a microservices architecture – often a key task in building a globally distributed application architecture – is challenging work, and brings inevitable misfires. by Mark Boyd, Dawn Foster, Chris Latimer [thenewstack.io]
Microservices :- the accidental architecture
My team adopted Microservices accidentally. As a result we’ve come to believe that Microservices are truly beneficial and that teams should adopt the approach not because they are the latest hot trend, but because they offer the best solution to the challenges facing most large development orgs. by John McClean [articles.microservices.com]
How Bustle Uses a Serverless Architecture to Manage 52 Million Monthly Visitors
Established tech companies are starting to look at migrating their production environments to serverless architectures. Case in point: Bustle, a media company aimed at millennial women. by Mark Boyd, Daniel Kahn, Brian Wheeler [thenewstack.io]
Want to share something?
As always, if you want to chat, share a link, or make a suggestion, feel free to drop us a quick note using Twitter (@launchany and @caseysoftware) or by emailing us at: email@example.com.