The Latest News On The API Economy
Searching: No Search Term , Filtered By Article Type: "Analysis"
When designing an enterprise architecture it can be common to use a typical Pub-Sub pattern using a message queue subscribed to a topic. This can have some real-world costs and queues may not be necessary. This article shows a better choice than using queues and when it makes sense to use a queue.
Angular 2, the Web application framework released in September 2016, is already proving to be leaps ahead of its predecessor. We examine what is working so far, what elements of the framework are still lacking, how it measures up to other frameworks and its outlook and implications for developers.
This is the final part of our series How to Add Postcode-Based Proximity Search With Open Data. After going through each of the steps, you're ready to build the app. In this part of our series we bring together the pieces and build a pub locating application that demonstrates how they work together.
Microservice architecture is a topic of conversation seemingly heard everywhere in today's technology landscape. While the exact definition can be hard to pinpoint, there are lessons to be learned from the trend. This article looks at lessons around scale, velocity and risk reduction.
As part of a continuing effort to publicize its move to microservices, Netflix open-sourced its code, allowing companies to use its libraries to build cloud-based microservices architectures. Here we highlight several Netflix open source software projects for building microservices architectures.
Once a distributed application is built and deployed, it is crucial to monitor and visualize it to make sure the software is reliable, available, and performs as expected. This article looks at several new API solutions that help providers address these issues for microservice architectures.
This is the introduction to our series What is The Green Button API initiative and How It Took OAuth To An Entirely New Level. This article will help you understand what the Green Button API Initiative is and how it came about. Green Button is part of the Obama Administration's My Data initiatives.
This is the first part of our series What is The Green Button API initiative and How It Took OAuth To An Entirely New Level. In this part we will take a look at some of the primary use cases of the initiative including the data custodian, third party entities and retail customers.
This is part 2 of our series on the Green Button API initiative. This article examines the architectural underpinnings, including the requirements and standards behind the initiative. The Green Button technology is based on existing standards that were assembled to meet the identified requirements.
This is part 3 of our series on the U.S. government's Green Button API initiative. In this part, we will describe the building blocks of Green Button technology and how they respond to the project requirements with respect to authorization of access to data provided to third parties.
This is part 4 of our series What is The Green Button API initiative and How It Took OAuth To An Entirely New Level. In this part we explain the structure of Green Buttons’ scope parameters and illustrate the data exchanges and protocol used to implement Green Button’s scope negotiation.
This is part 5 of our series What is The Green Button API initiative and How It Took OAuth To An Entirely New Level. Here, we look at how Green Button data, due to its regularly renewed nature needed to adopt a pseudo PUSH model that was consistent with the OAuth resource data exchange model.
This is the conclusion to our series What is The Green Button API initiative and How It Took OAuth To An Entirely New Level. It provides a set of references for enriched additional information for the reader about technologies and choices made in the design of the Green Button architecture.
While WebRTC is not a mainstream term it is the primary technology contender of the telephony world with more than 2 billion supported browsers. By following a Web model instead of a traditional Telco model. WebRTC eschews a requirement for interoperability in exchange for innovation and choice.
The 2016 presidential has been a hot topic of conversation in the past two weeks. Many issues came to light largely due to the many controversies surrounding the election. Many of the controversies were a result of fake news though, a real problem that technology must address.
The Second Payment Services Directive or PSD2 comes into effect January 13, 2018. This open banking initiative will no doubt be a game changer in Europe and really for any retail bank or fintech that wishes to work with Europe. Today we’ll give you an overview of what exactly PSD2 is. Then
For the fourth year in a row, WIP Factory is taking the pulse of the developer relations and developer program community with its annual Devrel Survey. If you work in developer relations or for a company's developer program you are welcome to participate. Deadline is November 21st!
APIs are critical to many platforms but don't get nearly the amount of QA that Web sites or apps receive. Many major API issues are surprisingly subtle and without proper testing they can sneak through the cracks. This article looks at four such issues and how they could have been avoided.
The Japanese have five essential elements of life, known as the Godai: Earth, Water, Fire, Wind and Void. In this article Rebrandly discusses what it feels are the five Godai elements that an amazing API requires: Design, Scalability, Reliability, Security and Documentation.
Taken together, API versioning and retirement constitute the last of the eight phases of API lifecycle management. They're also considered to be an art unto themselves. Taking that art to another level however could involve some new thinking that involves the idea of "microversioning."