Http notifications, what should one use these days?

<p>So, i am thinking to create a small pet project and one of the main parts of it would be to receive some http notifications from various services, parse these notifications, save some data, then forward them to other http urls that subscribed to get them(let&#39;s say a huge number here).</p> <p>Now, i know there are 3rd-party push services out there that can ease this work for me, but if i would like to implement this myself in go as an excercise, how would i go about it, any pointers related to the general workflow?</p> <hr/>**评论：**<br/><br/>ZetaHunter: <pre><p>What you are basically talking about I guess is web hooks? You would probably setup an http server with an endpoint that would accept POST with the notification and then check against your data store for subscribers and then just send it on to those subscribers.</p> <p>I don&#39;t really have any experience but have some interest in this so will subscribe for further comments.</p></pre>tmornini: <pre><blockquote> <p>an http server with an endpoint that would accept POST</p> </blockquote> <p>Or PUTs to avoid duplicate notifications...</p></pre>twisted1919: <pre><p>yup, webhooks. the question is more about what you&#39;d use as your stack to make this happen. having a http server accepting POST was something from the get-go.</p></pre>