Search
175 results for “oskardudycz”
-
Vertical Slices in software architecture are pictured right now as the best thing since sliced bread.
I won’t try to hide that, like it. I've written about CQRS and Vertical Slices over the years - how to slice the codebase effectively, shown examples, and explained why generic doesn't mean simple, yet…
I still get questions about Vertical Slices Architecture (VSA).
After a recent Discord discussion in the recent #ArchitectureWeekly, I want to share some additional thoughts on how I see Vertical Slices Architecture, how it relates to CQRS, what different slicing strategies are, and (of course) the tradeoffs.
But also why we love discussing it, and how Semantic Diffusion impacts that.
https://www.architecture-weekly.com/p/my-thoughts-on-vertical-slices-cqrs
-
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
-
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
-
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
-
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
-
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! 🙂
-
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! 🙂
-
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, 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, 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 ❤️
-
Most of the time, we discuss strong consistency and eventual consistency.
Most systems prefer to have strong consistency. You perform the operation, wait till it’s finished and then proceed.
Take adding attachment to your business processes as an example. We could handle uploads synchronously. User selects file → browser uploads to server → server stores file → server creates database record → server returns success.
Simple, consistent, slow.
This creates problems:
1. Large files block the UI for minutes.
2. Network interruptions force complete restarts.
3. Servers become bottlenecks, streaming every byte through memory.
4. Multi-gigabyte files can crash servers.Luckily, we learned that sometimes we have to live with an additional delay. Still, we should not stop that, as it’s a bit trickier than “a small delay”.
We usually assume that stuff will happen in a particular order, we just don’t know precisely when. And that’s actually something that’s called Causal Consistency. The difference between Eventual and Causal consistency is:
Eventual consistency - The system eventually reaches a consistent state. Order of operations doesn't matter. Create a link, then upload the file, or upload the file, then create the link - the result is the same. The system tolerates temporary inconsistency.
Causal consistency - Operations must respect cause and effect. You can't comment on a document before it exists. Effects follow causes.
File uploads fit eventual consistency perfectly. When attaching a blueprint to a construction task, two things happen: storing the file and linking it to the task. The order is irrelevant. What matters is that both are completed eventually.
With eventual consistency for file uploads, we can show files as "attached" immediately. The actual upload happens in the background. Of course, we won’t be able to download them until the upload is finished, but the system continues working during the brief inconsistency.
And that's also what I discussed today in details in the latest #ArchitectureWeekly.
I did a follow-up to last week's article about inverting dependency, this time expanding on how predictable ids can also help you to beat eventual consistency.
Read more: https://www.architecture-weekly.com/p/dealing-with-eventual-consistency
-
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!
-
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!