<h1 id="triggermesh">Triggermesh<a aria-hidden="true" class="anchor-heading icon-link" href="#triggermesh"></a></h1>
<p><a href="/wiki/notes/gvgsn1lhuzopukqfro9qofc">Event Broker</a></p>
<ul>
<li>url: <a href="https://www.triggermesh.com/">https://www.triggermesh.com/</a></li>
<li>written_in: go</li>
<li><a href="/wiki/notes/sXdbycnnhKoXF4wCWYlLo">supports</a> <a href="/wiki/notes/8cs1j4m6abso08lz9kxbef3">Cloudevents</a></li>
<li><a href="/wiki/notes/WI9Hye9uqF9yeOTTgKnY7">similarTo</a> <a href="/wiki/notes/p365jlmlu7knjy94z5bty44">Event Bridge</a></li>
</ul>
<ul>
<li>"TriggerMesh abstracts event brokers, event sources and event sinks. For brokers, you can swap whichever message streaming technology you want. You can use Kinesis, Kafka, Google PubSub, <del><a href="/wiki/notes/iypvlwhcbuwo79fm2uayixf">NATS</a></del>, and/or others."
<ul>
<li><a href="https://thenewstack.io/supercharging-event-driven-integrations-using-apache-kafka-and-triggermesh/">https://thenewstack.io/supercharging-event-driven-integrations-using-apache-kafka-and-triggermesh/</a></li>
<li>t.2024.03.31.12 can't find any references to NATS</li>
</ul>
</li>
<li>"FaaS can be thought of as the glue that connects cloud services together and that gets executed when certain events happen. Serverless enables developers to focus on applications that consist of event-driven functions that respond to a variety of triggers."
<ul>
<li>"<a href="https://www.triggermesh.com/blog/what-every-cio-needs-to-know-about-serverless-part-2%22">https://www.triggermesh.com/blog/what-every-cio-needs-to-know-about-serverless-part-2"</a></li>
</ul>
</li>
</ul>
<hr>
<strong>Backlinks</strong>
<ul>
<li><a href="/wiki/notes/8cs1j4m6abso08lz9kxbef3">Cloudevents</a></li>
<li><a href="/wiki/notes/p365jlmlu7knjy94z5bty44">Event Bridge</a></li>
</ul>

Triggermesh

public-notes


Welcome! And beware!  

## Purpose

This vault is the "[[learning-in-public|ar.swyx.learn-in-public]]" part of my Second Brain. If you share some of my interests, please [reach out](https://djradon.github.io)! 

## Contents

- [[t]] my personal wikipedia
- [[idea]] (not necessarily mine)
- Resource Notes, including highlights, thoughts and metadata, for various things:
  - [[ar]] mostly articles, papers and web pages
  - [[book]]
  - [[community]]
  - [[course]]
  - [[event]]
  - [[game]]
  - [[loc]]
  - [[org]]
  - [[user]] 
  - [[prdct]] mostly software products, but also ontologies
  - [[recipe]]
  - [[video]] movies, tv episodes, youtube, etc
- [[vs]]
- [[wanted]]
- Some "Metadata Notes":
  - [[tags]] which may refer to any and multiple (or none) of the above
  - [[c]]: ways to categorize resources
  - [[p]]: ways to assert things about resources (mostly abandoned)

In terms of the [[t.km.zettelkasten]] method, this wiki is a commingling of literature notes with something @Sönke-Ahrens warned about: a "personal Wikipedia or a database" [^1]. 

In terms of [[t.tm.getting-things-done]], it's references, someday-maybe, next actions, and public projects.

## Beware!

This is a cluttered cupboard of jumbled jottings riddled with inaccuracies, confusion, and mistakes.

## What This Is Not

- evergreen-notes/digital-garden: for "synthesized" / original-ish publishable big-idea notes that should evolve over time, props to @andy-matuschak and @maggie-appleton
- blog: for "point-in-time" items to be shared: personal news, articles, etc.
  - e.g., [[ar.substack.carpe-noctem]]


[^1]: [[book.how-to-take-smart-notes]]  