4 ms·

I can only speak about Mulesoft. It is expensive. If you are running mission critical stuff then you can justify the cost. That is we outsourced disaster planni

I can only speak about Mulesoft. It is expensive. If you are running mission critical stuff then you can justify the cost. That is we outsourced disaster planning and recovery to them. They are essentially hosting APIs for you. Personally I believe APIs peak has past. Developers want to deliver functionality quickly. Seems to me, people are looking for ways to bypass APIs. E.g., webhooks, event architectures like Kafka. etc. That is instead of exposing an API for the entire internet to hit. Modern architectures are more selective or direct or has less intermediaries.

Mandatum 4y ago
Do you mean RESTful and RPC-based APIs peak has past? Because in the backend, everyone's still using and building those, it's just the way they're advertising and mainly doing integration is event-based (which sometimes is actually just RPC wrapped in a long-polling mechanism). Or do you not see event-based architectures as APIs?
- varunjsr7 4y ago
  Looks like we are saying the same thing :)
- rawgabbit 4y ago
  Sorry, let me try to be more clear. I believe people are exploring ways to move beyond and no longer have the need for APIs. Webhooks and event architectures are, I believe, stepping stones towards that goal. That is instead of an architecture that relies on multiple APIs to interact in near real-time. I believe the direction is fewer services that interact with each other asynchronously. And their coordination will be by a Kafka type event log.
  - Mandatum 4y ago
    I agree, once we've removed the functional, silo'd data stores that have currently been built as services and we migrate from proprietary or silo'd service to centralised event-log we've.. Come full circle and arrived at fucking event bus' from the 80s. Sounds like SOA on MQ.
varunjsr7 4y ago
I 100% agree with your opinion and it makes total sense to go with minimal intermediaries! I'm trying to decipher your comment around "bypass APIs" - the webhook and event streaming arch. makes sense for any net new applications being built from now (or for the past few years). A typical small to medium enterprise would still have hundreds of APIs (internal and external) that still need a platforms to take care of API lifecycle events. My follow-up question is as follows - Is there a market for another API management tool that is 1. Less expensive, 2. Encourages collaboration between internal dev teams, 3. Curation i.e. takes care of the lifecycle management i.e. design, arch. approval, development, test, release, production, versioning, monitoring, deprecation. 4. Compliance - PCI compliant and manage clientIDs and secrets (rotation included) 5. Be multi cloud-native
- rawgabbit 4y ago
  I believe the trend is micro services using Kafka based event messaging with minimal APIs.

Mandatum 4y ago

Do you mean RESTful and RPC-based APIs peak has past? Because in the backend, everyone's still using and building those, it's just the way they're advertising and mainly doing integration is event-based (which sometimes is actually just RPC wrapped in a long-polling mechanism). Or do you not see event-based architectures as APIs?

varunjsr7 4y ago
Looks like we are saying the same thing :)
rawgabbit 4y ago
Sorry, let me try to be more clear. I believe people are exploring ways to move beyond and no longer have the need for APIs. Webhooks and event architectures are, I believe, stepping stones towards that goal. That is instead of an architecture that relies on multiple APIs to interact in near real-time. I believe the direction is fewer services that interact with each other asynchronously. And their coordination will be by a Kafka type event log.
- Mandatum 4y ago
  I agree, once we've removed the functional, silo'd data stores that have currently been built as services and we migrate from proprietary or silo'd service to centralised event-log we've.. Come full circle and arrived at fucking event bus' from the 80s. Sounds like SOA on MQ.

varunjsr7 4y ago

I 100% agree with your opinion and it makes total sense to go with minimal intermediaries! I'm trying to decipher your comment around "bypass APIs" - the webhook and event streaming arch. makes sense for any net new applications being built from now (or for the past few years). A typical small to medium enterprise would still have hundreds of APIs (internal and external) that still need a platforms to take care of API lifecycle events. My follow-up question is as follows - Is there a market for another API management tool that is 1. Less expensive, 2. Encourages collaboration between internal dev teams, 3. Curation i.e. takes care of the lifecycle management i.e. design, arch. approval, development, test, release, production, versioning, monitoring, deprecation. 4. Compliance - PCI compliant and manage clientIDs and secrets (rotation included) 5. Be multi cloud-native

rawgabbit 4y ago
I believe the trend is micro services using Kafka based event messaging with minimal APIs.