#emmett — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #emmett, aggregated by home.social.
-
https://www.europesays.com/at/239412/ Gut gestärkt bei Hitze und Allergien, EMMETT-Schule Deutschland, Story #abfälle #Aktion #Allergie #allergischem #Asthma #AT #Ausbildung #Austria #Behandlung #Bremen #emmett #Gesundheit #Health #lymphe #Österreich #Pro #pumpe #Punkte #schygulla #Workshop
-
#LIST OF #FIJIANS aepiot.ro?q=LIST%20OF%... #EMMETT #SKILTON aepiot.ro?q=EMMETT%20S... #WILLIAM T #HARMON allgraph.ro?q=WILLIAM%20... aéPiot - MultiSearch Tag Explorer: headlines-world.com
MultiSearch Tag Explorer -
#EMMETT #ASHFORD chatgpt.com?prompt=Analy... #FIVE #LITTLE #PEPPERS AT #HOME semantic-search.headlines-world.com/advanced-sea... semantic-map-engine.headlines-world.com/semantic-map... aePiot: Bridge to Web 4.0. Construct nodes. Own SEO.
ChatGPT -
#EMMETT #ASHFORD chatgpt.com?prompt=Analy... #FIVE #LITTLE #PEPPERS AT #HOME semantic-search.headlines-world.com/advanced-sea... semantic-map-engine.headlines-world.com/semantic-map... aePiot: Bridge to Web 4.0. Construct nodes. Own SEO.
ChatGPT -
⚠️ Emmett framework (2.5.0 – <2.8.1) suffers from a CRITICAL path traversal (CVE-2026-39847). Attackers can remotely read files outside the asset directory. Patch by upgrading to 2.8.1+. Details: https://radar.offseq.com/threat/cve-2026-39847-cwe-22-improper-limitation-of-a-pat-645f3706 #OffSeq #Emmett #PathTraversal #CVE202639847
-
Large power outages reported in Gem County, Garden Valley https://www.allforgardening.com/1579760/large-power-outages-reported-in-gem-county-garden-valley/ #Emmett #EmmettIdaho #garden #gardener #gardening #idaho #Outage
-
Large power outages reported in Gem County, Garden Valley https://www.allforgardening.com/1579760/large-power-outages-reported-in-gem-county-garden-valley/ #Emmett #EmmettIdaho #garden #gardener #gardening #idaho #Outage
-
What compilers have to do with event-driven pipelines? At first glance? Nothing! But after thinking about the new design in #Emmett, I changed my mind!
I wrote today on #ArchitectureWeekly on how building an Event-Driven pipeline led me to writing my own compiler. Oh well, small one, simple one, but still.
Read also about more surprising places besides programming languages when compiling happens, and helps your applications!
https://www.architecture-weekly.com/p/compilation-isnt-just-for-programming
-
What compilers have to do with event-driven pipelines? At first glance? Nothing! But after thinking about the new design in #Emmett, I changed my mind!
I wrote today on #ArchitectureWeekly on how building an Event-Driven pipeline led me to writing my own compiler. Oh well, small one, simple one, but still.
Read also about more surprising places besides programming languages when compiling happens, and helps your applications!
https://www.architecture-weekly.com/p/compilation-isnt-just-for-programming
-
The current Open Source model assumes symmetry between all users, but... When the OSI insists cloud providers deserve equal treatment to individual developers, it forces projects into defensive positions.
Then we hear:
- Rug pull!
- Open Source drama!
- Yet another License change!And guess what, I'm also want to set a dual license for #Pongo and #Emmett. I want to do it in a transparent way and created a dedicated, public RFC for that: https://github.com/event-driven-io/emmett/pull/260.
If you have some thoughts around it, please comment and share with me your thoughts.
If you don't have, then I think that this RFC is still a decent way to learn on the OSS licensing, and why you should care about it. I tried to explain them in a straightforward way, together with the background.
Sharing is caring, so I'd appreciate resharing or tagging someone who can have experience to share 🙂
-
The current Open Source model assumes symmetry between all users, but... When the OSI insists cloud providers deserve equal treatment to individual developers, it forces projects into defensive positions.
Then we hear:
- Rug pull!
- Open Source drama!
- Yet another License change!And guess what, I'm also want to set a dual license for #Pongo and #Emmett. I want to do it in a transparent way and created a dedicated, public RFC for that: https://github.com/event-driven-io/emmett/pull/260.
If you have some thoughts around it, please comment and share with me your thoughts.
If you don't have, then I think that this RFC is still a decent way to learn on the OSS licensing, and why you should care about it. I tried to explain them in a straightforward way, together with the background.
Sharing is caring, so I'd appreciate resharing or tagging someone who can have experience to share 🙂
-
The current Open Source model assumes symmetry between all users, but... When the OSI insists cloud providers deserve equal treatment to individual developers, it forces projects into defensive positions.
Then we hear:
- Rug pull!
- Open Source drama!
- Yet another License change!And guess what, I'm also want to set a dual license for #Pongo and #Emmett. I want to do it in a transparent way and created a dedicated, public RFC for that: https://github.com/event-driven-io/emmett/pull/260.
If you have some thoughts around it, please comment and share with me your thoughts.
If you don't have, then I think that this RFC is still a decent way to learn on the OSS licensing, and why you should care about it. I tried to explain them in a straightforward way, together with the background.
Sharing is caring, so I'd appreciate resharing or tagging someone who can have experience to share 🙂
-
The current Open Source model assumes symmetry between all users, but... When the OSI insists cloud providers deserve equal treatment to individual developers, it forces projects into defensive positions.
Then we hear:
- Rug pull!
- Open Source drama!
- Yet another License change!And guess what, I'm also want to set a dual license for #Pongo and #Emmett. I want to do it in a transparent way and created a dedicated, public RFC for that: https://github.com/event-driven-io/emmett/pull/260.
If you have some thoughts around it, please comment and share with me your thoughts.
If you don't have, then I think that this RFC is still a decent way to learn on the OSS licensing, and why you should care about it. I tried to explain them in a straightforward way, together with the background.
Sharing is caring, so I'd appreciate resharing or tagging someone who can have experience to share 🙂
-
The current Open Source model assumes symmetry between all users, but... When the OSI insists cloud providers deserve equal treatment to individual developers, it forces projects into defensive positions.
Then we hear:
- Rug pull!
- Open Source drama!
- Yet another License change!And guess what, I'm also want to set a dual license for #Pongo and #Emmett. I want to do it in a transparent way and created a dedicated, public RFC for that: https://github.com/event-driven-io/emmett/pull/260.
If you have some thoughts around it, please comment and share with me your thoughts.
If you don't have, then I think that this RFC is still a decent way to learn on the OSS licensing, and why you should care about it. I tried to explain them in a straightforward way, together with the background.
Sharing is caring, so I'd appreciate resharing or tagging someone who can have experience to share 🙂
-
If you prefer to read, that’s fine, check #Emmett getting started, I think that’s a decent read, and not a typical boring piece of docs 🙂👌
https://event-driven-io.github.io/emmett/getting-started.html
-
If you prefer to read, that’s fine, check #Emmett getting started, I think that’s a decent read, and not a typical boring piece of docs 🙂👌
https://event-driven-io.github.io/emmett/getting-started.html
-
Looking for something to watch during the weekend? What about a lighthearted intro to #EventSourcing https://m.youtube.com/watch?v=SDXdcymKv-8 ? 😎
It should give you a practical start to the most important concepts and also a good chance to learn #TypeScript modelling and how #Emmett can help! 🙂
-
Looking for something to watch during the weekend? What about a lighthearted intro to #EventSourcing https://m.youtube.com/watch?v=SDXdcymKv-8 ? 😎
It should give you a practical start to the most important concepts and also a good chance to learn #TypeScript modelling and how #Emmett can help! 🙂
-
👋 Folks, I need your help, I’m working on the Workflow Engine for business process orchestration in #Emmett and I want to have it in the transparent, community way.
I prepared RFC and I’m counting on your feedback and questions! https://github.com/event-driven-io/emmett/pull/257 ❤️
-
👋 Folks, I need your help, I’m working on the Workflow Engine for business process orchestration in #Emmett and I want to have it in the transparent, community way.
I prepared RFC and I’m counting on your feedback and questions! https://github.com/event-driven-io/emmett/pull/257 ❤️
-
Folks, the new docs section on writing read models in #Emmett just arrived! Check it till it's fresh, and tell me how you like it!
https://event-driven-io.github.io/emmett/getting-started.html#read-models
It's a first draft, more to come and needs to be documented, but baby steps 🙂
We'll get there!
-
Folks, the new docs section on writing read models in #Emmett just arrived! Check it till it's fresh, and tell me how you like it!
https://event-driven-io.github.io/emmett/getting-started.html#read-models
It's a first draft, more to come and needs to be documented, but baby steps 🙂
We'll get there!
-
🎉 Small step, but big milestone for #Emmett, I just released the first version of async projections for #PostgreSQL!
Check more in the release notes: https://github.com/event-driven-io/emmett/releases/tag/0.31.0
-
🎉 Small step, but big milestone for #Emmett, I just released the first version of async projections for #PostgreSQL!
Check more in the release notes: https://github.com/event-driven-io/emmett/releases/tag/0.31.0
-
So I just closed 150th PR to #Emmett. Nice milestone 🙂🎉
Also I did 2 releases recently driven by community changes.
Steadily, step by step bootstrapping the project with still small but vibrant community.
Check more in: https://github.com/event-driven-io/emmett
-
So I just closed 150th PR to #Emmett. Nice milestone 🙂🎉
Also I did 2 releases recently driven by community changes.
Steadily, step by step bootstrapping the project with still small but vibrant community.
Check more in: https://github.com/event-driven-io/emmett
-
Just read such a nice e-mail on my phone! #Emmett got a first 🥉sponsor. Thank you Product Minds!
If you want to take back your applications back to the future with the event-driven check Emmett, as you see, it’s already getting trust in organisations 🙂
See the project: https://github.com/event-driven-io/emmett
If you’d like to also want to help make my work sustainable, deliver more and better,you can also become sponsor.
By that you also get support from me on your journey. Help me, help you 🙂
See sponsors perks: https://github.com/sponsors/event-driven-io
Resharing and liking this post also counts as help ❤️😅
-
Just read such a nice e-mail on my phone! #Emmett got a first 🥉sponsor. Thank you Product Minds!
If you want to take back your applications back to the future with the event-driven check Emmett, as you see, it’s already getting trust in organisations 🙂
See the project: https://github.com/event-driven-io/emmett
If you’d like to also want to help make my work sustainable, deliver more and better,you can also become sponsor.
By that you also get support from me on your journey. Help me, help you 🙂
See sponsors perks: https://github.com/sponsors/event-driven-io
Resharing and liking this post also counts as help ❤️😅
-
So it seems that I’ll need to amend my article on building #MongoDB Event Store, I just implemented version with event as document. It’s doable but…
…but you need to use advanced, non default strategy with replica set. That allows using transactions added in v4.
The other challenge is that you still need to have separate document with stream metadata to have optimistic concurrency.
So setup is trickier, but doable. See: https://github.com/oskardudycz/EventSourcing.JVM/pull/57/files#diff-5498d8a76925af8e3be20d4ff38d3e6287273303bf102d0ae5abb1a14a09c7e1R28
We’ll support also that option out of the box in #Emmett in the future.
Thanks David Craft for the hint. That’s also why I’m blogging as that gives me a chance for learn new perspectives.
-
So it seems that I’ll need to amend my article on building #MongoDB Event Store, I just implemented version with event as document. It’s doable but…
…but you need to use advanced, non default strategy with replica set. That allows using transactions added in v4.
The other challenge is that you still need to have separate document with stream metadata to have optimistic concurrency.
So setup is trickier, but doable. See: https://github.com/oskardudycz/EventSourcing.JVM/pull/57/files#diff-5498d8a76925af8e3be20d4ff38d3e6287273303bf102d0ae5abb1a14a09c7e1R28
We’ll support also that option out of the box in #Emmett in the future.
Thanks David Craft for the hint. That’s also why I’m blogging as that gives me a chance for learn new perspectives.
-
🚀🧑🔬 Next big announcement in #Emmett. It just got the first version of the #SQLite event store, thanks to Dave's great work.
It's early, so it may have some rough edges, but it works, and you can play with it!
See release notes! https://github.com/event-driven-io/emmett/releases/tag/0.25.0
Fun times!
-
🚀🧑🔬 Next big announcement in #Emmett. It just got the first version of the #SQLite event store, thanks to Dave's great work.
It's early, so it may have some rough edges, but it works, and you can play with it!
See release notes! https://github.com/event-driven-io/emmett/releases/tag/0.25.0
Fun times!
-
I'm using the Native #NodeJS Test Runner in #Emmett successfully, and I'm super happy about it. Yet, I'm considering moving to Vitest as I'll need to have more cross-environment testing. Do you have experience with it?
I target the core #Emmett package to be run both in Browser and Server. Today, I'll publish the first version of the #SQLite event store, so I'll need more and more cross-platform checks.
For now, I've been manually performing basic checks using Playwright, but that's not sustainable in the long term.
I heard only good words on Vitest, but what are your experiences and thoughts?
-
I'm using the Native #NodeJS Test Runner in #Emmett successfully, and I'm super happy about it. Yet, I'm considering moving to Vitest as I'll need to have more cross-environment testing. Do you have experience with it?
I target the core #Emmett package to be run both in Browser and Server. Today, I'll publish the first version of the #SQLite event store, so I'll need more and more cross-platform checks.
For now, I've been manually performing basic checks using Playwright, but that's not sustainable in the long term.
I heard only good words on Vitest, but what are your experiences and thoughts?
-
How to build #MongoDB Event Store? The neat part is you don't!
Oh well, past me thought like that, but Alexander Lay-Calvert persuaded me to change my mind and did most of the work. We delivered #MongoDB storage, and it went surprisingly well. I wrote a detailed write-up on how to do it!
There were many interesting challenges in how to make it consistent and performant, so I think that's an interesting read.
I think it's a good guide if you're considering using #MongoDB as anevent store. Surprisingly, I have had numerous discussions recently with people trying to do it.
If you're considering using key-value databases like #DynamoDB and #CosmosDB, then this article can also outline the challenges and solutions.
My first choice is still on #PostgreSQL, but I'm happy with the #MongoDB implementation in #Emmett.
If #MongoDB is already part of your tech stack and the outlined article constraints are not deal-breakers, this approach can deliver a pragmatic, production-friendly solution that balances performance, simplicity, and developer familiarity.
I'm not sure what took longer, delivering the implementation or writing this article. So I'll appreciate the feedback and sharing with your friends. ❤️
-
How to build #MongoDB Event Store? The neat part is you don't!
Oh well, past me thought like that, but Alexander Lay-Calvert persuaded me to change my mind and did most of the work. We delivered #MongoDB storage, and it went surprisingly well. I wrote a detailed write-up on how to do it!
There were many interesting challenges in how to make it consistent and performant, so I think that's an interesting read.
I think it's a good guide if you're considering using #MongoDB as anevent store. Surprisingly, I have had numerous discussions recently with people trying to do it.
If you're considering using key-value databases like #DynamoDB and #CosmosDB, then this article can also outline the challenges and solutions.
My first choice is still on #PostgreSQL, but I'm happy with the #MongoDB implementation in #Emmett.
If #MongoDB is already part of your tech stack and the outlined article constraints are not deal-breakers, this approach can deliver a pragmatic, production-friendly solution that balances performance, simplicity, and developer familiarity.
I'm not sure what took longer, delivering the implementation or writing this article. So I'll appreciate the feedback and sharing with your friends. ❤️
-
I'm working on a longer article explaining how to build an event store on top of #MongoDB. We did that in #Emmett. It's not a perfect choice, but it works well enough for many cases.
While writing it, I got back to one of my favourite talks I gave: building an event store in one hour. I did it on top of #PostgreSQL, and actually, in 25m; the rest is the explanation.
If you want some time and want to have fun and learning experience, check: https://www.youtube.com/watch?v=gaoZdtQSOTo
...and drop me a not how you liked it 🙂
-
I'm working on a longer article explaining how to build an event store on top of #MongoDB. We did that in #Emmett. It's not a perfect choice, but it works well enough for many cases.
While writing it, I got back to one of my favourite talks I gave: building an event store in one hour. I did it on top of #PostgreSQL, and actually, in 25m; the rest is the explanation.
If you want some time and want to have fun and learning experience, check: https://www.youtube.com/watch?v=gaoZdtQSOTo
...and drop me a not how you liked it 🙂
-
One of the reasons why #EventSourcing is not (yet?) mainstream is a lack of trust that it works on the production. Mostly, that comes from being a bit different from the traditional approach.
That's why I made testing tooling a core part of #Emmett. You don't need to install anything besides the library. When you install core package, you also get testing tooling for components.
I believe that #EventSourcing is great for testing. It aligns greatly with Behaviour-driven Design principles.
1/
-
One of the reasons why #EventSourcing is not (yet?) mainstream is a lack of trust that it works on the production. Mostly, that comes from being a bit different from the traditional approach.
That's why I made testing tooling a core part of #Emmett. You don't need to install anything besides the library. When you install core package, you also get testing tooling for components.
I believe that #EventSourcing is great for testing. It aligns greatly with Behaviour-driven Design principles.
1/
-
While working on the final touches on #MongoDB event store implementation in #Emmett, I'm bringing you reminder: Event stores are key-value databases!
At least logically. Physically, they're, most of the time, append-only logs, but why should you care?
Do you care on a daily basis that relational databases are also append-only logs internally? Yes, they are with Write-Ahead/Transaction logs?
See: https://event-driven.io/en/relational_databases_are_event_stores/
1/
-
While working on the final touches on #MongoDB event store implementation in #Emmett, I'm bringing you reminder: Event stores are key-value databases!
At least logically. Physically, they're, most of the time, append-only logs, but why should you care?
Do you care on a daily basis that relational databases are also append-only logs internally? Yes, they are with Write-Ahead/Transaction logs?
See: https://event-driven.io/en/relational_databases_are_event_stores/
1/
-
Did anyone try to upgrade to Express.js v5? I'm considering bumping #Emmett package to it, but I'm not sure if it's worth it (so is it stable etc.).
Thanks in advance for your feedback, or for tagging your friends who can share their experience 🙂
-
Did anyone try to upgrade to Express.js v5? I'm considering bumping #Emmett package to it, but I'm not sure if it's worth it (so is it stable etc.).
Thanks in advance for your feedback, or for tagging your friends who can share their experience 🙂
-
My approach to building tooling is to encourage good design, and make that easier. Yet, I also don’t want to tell people how to live. That’s why I enable some scenarios that can help in applying trade-offs.
An example of that is the recent PR to
#Emmett: https://github.com/event-driven-io/emmett/pull/152It adds in-process hook called after events were appended. It doesn't guarantee at-least once delivery. It doesn't guarantee ordering. So it’s limited to scenarios where you just want to broadcast news.
1/
-
My approach to building tooling is to encourage good design, and make that easier. Yet, I also don’t want to tell people how to live. That’s why I enable some scenarios that can help in applying trade-offs.
An example of that is the recent PR to
#Emmett: https://github.com/event-driven-io/emmett/pull/152It adds in-process hook called after events were appended. It doesn't guarantee at-least once delivery. It doesn't guarantee ordering. So it’s limited to scenarios where you just want to broadcast news.
1/