kenfdev

<p><span class="embed-block zenn-embedded zenn-embedded-card"><iframe id="zenn-embedded__33fb7f8f236b6" src="https://embed.zenn.studio/card#zenn-embedded__33fb7f8f236b6" data-content="https%3A%2F%2Fchangelog.com%2Fgotime%2F179" frameborder="0" scrolling="no" loading="lazy"></iframe></span><a href="https://changelog.com/gotime/179" style="display:none" target="_blank" rel="nofollow noopener noreferrer">https://changelog.com/gotime/179</a></p>
<p>Event-driven systems</p>
<ul>
<li>what it is
<ul>
<li>system architecture</li>
<li>uses asynchronous messaging to communicate state</li>
<li>example
<ul>
<li>user signup and pay for plan -&gt; unlock happens to account
<ul>
<li>talk to service?</li>
<li>use events?</li>
</ul>
</li>
</ul>
</li>
</ul>
</li>
<li>benifits
<ul>
<li>performance pump
<ul>
<li>handle thousands of messages asynchronously
<ul>
<li>whereas
<ul>
<li>synchronous architecture
<ul>
<li>tethered to IO</li>
</ul>
</li>
</ul>
</li>
</ul>
</li>
</ul>
</li>
</ul>
</li>
<li>event bus
<ul>
<li>message broker
<ul>
<li>queue
<ul>
<li>RabbitMQ</li>
<li>MQTT</li>
<li>NATS</li>
<li>Kafka</li>
<li>GCP Pub/Sub</li>
</ul>
</li>
</ul>
</li>
</ul>
</li>
<li>Eventual Consistency
<ul>
<li>Idenpotency
<ul>
<li>You should expect an event to accidentally happen more than once</li>
</ul>
</li>
</ul>
</li>
<li>starter project
<ul>
<li>production system
<ul>
<li>Kafka</li>
</ul>
</li>
<li>rabbitMQ and protobuf</li>
<li>etcd
<ul>
<li>cache layer</li>
</ul>
</li>
</ul>
</li>
<li>Continuous Deployment
<ul>
<li>don't just throw it over the wall</li>
<li>you own the thing, you built it, you know how it works you are the best person to see it to its conclusion essentially</li>
</ul>
</li>
</ul>
