subomi

10 ms·

91.
How to Make an Impact as a Platform Product Manager(theplatformspace.substack.com)
1 points by subomi 4y ago|0 comments
92.
Webhook Gateways for Platform Engineers(getconvoy.io)
3 points by subomi 4y ago|0 comments
93.
Who Benefits from Platform Engineering?(medium.com)
3 points by subomi 4y ago|0 comments
94.
Platform Engineering Guide: Principles and Best Practices(infoq.com)
1 points by subomi 4y ago|0 comments
95.
by subomi 4y ago
It seems the organisation was flagged. See here [0] [0] https://github.com/community/community/discussions/48173
96.
Webhooks with message brokers and Convoy(getconvoy.io)
30 points by subomi 4y ago|2 comments
97.
Don't call it a platform: Down with The Platform, up with Developer Enablement(samnewman.io)
3 points by subomi 4y ago|0 comments
98.
Slowing Down to Speed Up – Circuit Breakers for Slack’s CI/CD(slack.engineering)
1 points by subomi 4y ago|0 comments
99.
RedHat Generates $1B ARR(twitter.com)
2 points by subomi 4y ago|0 comments
100.
by subomi 4y ago
Not at the moment. But this is currently on our roadmap. See here [1] [1] https://github.com/orgs/frain-dev/projects/3
101.
by subomi 4y ago
That's exactly what Convoy is. It's open source and supports both directions of webhooks. Receiving and Sending. See here [1] to get started receiving. [1] https://getconvoy.io/docs/getting-started/receiv
102.
by subomi 4y ago
Hey! Convoy Founder here. The way we think about it is API Gateways are the entry point to your API. Webhook Gateways are the exit point to the API. Hence the name. :)
103.
The era of AI-first products(moreentropy.com)
2 points by subomi 4y ago|0 comments
104.
Fusion(usefusion.app)
1 points by subomi 4y ago|0 comments
105.
Code Speaks; Love the Code(joeduffyblog.com)
1 points by subomi 4y ago|0 comments
106.
Lets replicate pagerduty v3 webhooks in convoy(getconvoy.io)
8 points by subomi 4y ago|0 comments
107.
Enterprise Webhooks with Static Ips(github.com)
6 points by subomi 4y ago|0 comments
108.
Ask HN: Is ordering webhook events important to you and why?
4 points by subomi 4y ago|0 comments
109.
by subomi 4y ago
If you specify one public key for all endpoints, It means all consumers can verify each other’s webhook data which is not what you want. You want each consumer to be able to verify only webhooks intended for them and fail otherwise. We wrot
110.
by subomi 4y ago
Convoy author here. We also provide Signature verification. Static IPs are added security mechanisms for webhook consumers with strict network access rules.
111.
In Memory of a Giant(tenderlovemaking.com)
3 points by subomi 4y ago|0 comments
112.
Go and SQLite in the Cloud(golang.dk)
145 points by subomi 4y ago|118 comments
113.
by subomi 4y ago
Can anyone confirm this to be true, though? It seems everyone is recycling the same Bloomberg news :facepalm:
114.
by subomi 5y ago
Nice! Thanks for the context, super helpful. Yes, I am putting this on the roadmap! :)
115.
by subomi 5y ago
Hmm. To clarify, do you mean Postgres as a queueing backend or storage backend? We have it planned for a storage backend but not for queueing at the moment.
116.
by subomi 5y ago
Yes, infact a distributed broker will be a better option. But some of these users like the visibility Convoy's UI provides and since they currently do this inter-service communication with a HTTP Post, they prefer to put Convoy in the
117.
by subomi 5y ago
It's the similar differentiation with Svix. They're both largely SaaS based as of today. Convoy is largely OSS based. With a simple brew install you can publish events with Convoy from your local machine. :)
118.
by subomi 5y ago
Hmm. That sounds more concise. Thanks for the feedback!
119.
by subomi 5y ago
Oh, for clarity we do not support an in memory storage. We support an on disk storage & in memory queue. This enables the storage layer persist events across restarts.
120.
by subomi 5y ago
Thanks! If you can please paste the error here, so we can look into it.

More ›