“In today’s cloud computing world, many Product Managers will be faced with the decision of whether to open an API to their users. Open APIs have many advantages, but they also bring significant business challenges. In this post, I describe key benefits and challenges of open APIs, and why Product Managers should treat an open API as its own product instead of as a feature.”
Daniel Elizalde on Managers Build.
I’m in agreement with Daniel on this concept of productising an open API, whether that’s from the perspective of carriers offering this product to their customers or OSS vendors to carriers to offer to their customers.
Daniel also goes on to quote the following advantages of exposing your API:
I’d also add that:
But importantly, we need to discuss the challenges / pitfalls of introducing an open API as well. We’ll discuss more about these tomorrow.
Earlier this week, I was lucky enough to be introduced to a talented RAN automation expert. He’s one of Australia’s foremost, hands-on, experts on SON
I was listening to a group of telco experts on a podcast the other day. As they were talking, I kept picturing the image of
Earlier in the year, we wrote a series of articles about the chasm that exists between OSS/BSS buyers and sellers (pt1, pt2, pt3, pt4, pt5, pt6). “The chasm” is
Actually, maybe a few related questions. As you’ve seen from recent articles such as this, I’m increasingly interested in the cross-over worlds of comms and
Here at Passionate About OSS, we are exactly that – Passionate About OSS (Operational Support Systems). We’re also passionate about BSS, NMS, or any other names you call the tools that help to operationalise your network.
