Search
120 results for “oskardudycz”
-
So I just casually merged such a small Pull Request extending „a bit” my workshop exercises in #Java.
https://github.com/oskardudycz/EventSourcing.JVM/pull/58
Wanna see how to implement event stores on top of #PostgreSQL or #Mongo? How to use #EventStoreDB? Why not!
I’m going to have a few open and private workshops teaching #EventSourcing in practice. You can also join them or schedule one.
Or, you can try to do exercises as a self-paced kit, as I’m always open sourcing all of them. That’s not the full workshop experience, but can be good enough 🙂
-
Yesterday, I bragged about my #EventSourcing samples for #dotnet. I also promised that I'm not going to stop on that. So I won't!
Today, I modernised my #NodeJs samples. If you're looking for how to start your journey with #EventSourcing, then start with my repo: https://github.com/oskardudycz/EventSourcing.NodeJS
Now it uses the latest #NodeJs, #EventStoreDB, etc!
-
#EventSourcing in #Java?
Full sample with #SpringBoot?
Why not!
I just upgraded my Java samples to #SpringBoot 3 and #EventStoreDB 4: https://github.com/oskardudycz/EventSourcing.JVM/pull/38.
If you're looking for a place where:
- you could learn #EventSourcing from scratch with the self-paced kit,
- you can learn how to handle distributed processes, uniqueness, versioning,
- see real-world samples orchestrating that together.Then I think my repo is a decent place to start your journey!
-
I just applied #OpenTelemetry to my #EventSourcing in #dotnet samples: https://github.com/oskardudycz/EventSourcing.NetCore/pull/181.
It needs enhancements (especially around events, error handling, tagging etc.) but basic flow together with propagation is working fine for #Marten, #Kafka and #EventStoreDB.
Check it up! Feedback is more than welcome 😊
-
Hey @oskardudycz,
thanks for doing the hard work of digging into parts of Npgsql that we haven't documented yet. I've responded in your PR.
You'll have to replace the call to Npgsql.Replication.Internal.LogicalReplicationConnectionExtensions.CreateLogicalReplicationSlot() at https://github.com/oskardudycz/PostgresOutboxPatternWithCDC.NET/blob/master/PostgresOutbox/Subscriptions/EventsSubscription.cs#L42 with a call to Npgsql.Replication.PgOutputConnectionExtensions.CreatePgOutputReplicationSlot() and then everything should work without patching #Npgsql. -
To close this, we‘re using subscriptions from #eventstoredb with stored checkpoints (thx @oskardudycz for showing me), each achievement has their own subscription. The consumed events (finished cards) trigger the checks (if achievements have been reached). This enables to introduce new achievements that are granted to players in retrospective.
5/5
-
Friday, what a wonderful day! The day when another work week comes to an end, and the day when I wrote my first ever article, so now you have something to spend the weekend on reading about #dotnet, #reactiveui, #avaloniaui, and properties because it's all about them!
Without @oskardudycz and @thephd that work wouldn't be done at the level where it's now. Thank you for helping me in polishing it and suggesting improvements!
-
@tanepiper
#WebSerialAPI looks like a great idea. Then think about the potenti al dangers of browsers running on machines operating industrial apparatuses. The consequences could be devastating. In that cases it is much much better to provide a local application that would serve an API. It is still potentially hackable but it greatly reduce the exposed surface
@ColetteDiskette @oskardudycz -
Btw. It's the 101st closed Pull Request in #Pongo. Chef kiss 👌😎
-
#Pongo just reached 1300 🌟 on GitHub! Nice!
If you’d like to match #MongoDB accessibility with #PostgreSQL powers - try it!
-
Sneaky code bites back, I realised that again recently.
I realised I'd been writing terrible code when I couldn't explain it to myself.
The code worked. It was adding SQLite support to Pongo. But when I tried to describe how I was implementing multi-database support, I heard myself saying:
"First it checks if the Promise is cached, then it creates a proxy that defers to the real implementation which doesn't exist yet, but will be loaded dynamically when..."
Insane, I was going insane.
It's a pattern we all fall into.
We see repetition and think, "I can abstract this."
We see explicit configuration and think: "I can infer this". We see upfront costs and think: "I can defer this".
Sometimes we just don’t trust our colleagues, thinking that they’re too incompetent and we need to take precautionary steps.
Sometimes we're right. Most often we’re not.
Too often, we're optimising the wrong metric. I was optimising for fewer imports, not simpler code. I was hiding essential configuration, not accidental complexity.
A minimal API with complex implementation isn't simple—it's a lie. The complexity doesn't disappear. It moves from the visible surface to hidden internals, where it's harder to understand, debug, and modify.
I got too clever. We all do sometimes. The key is catching it before it escapes into production, where it becomes someone else's nightmare.
Now I'm removing this code, and that's fine.
Want to read details? Check the latest #ArchitectureWeekly https://www.architecture-weekly.com/p/sneaky-code-bites-back
And tell me about your sneakiness.
How hard did it bite you?
-
Me ATM fighting with the #TypeScript generics while reshaping #Pongo API 😅
-
Do you want to learn more about cool #PostgreSQL features like partitioning, logical replication? Know also more about dos and dont's from my experience?
After receiving a ton of questions on last week's Particular Software webinar on #PostgreSQL Superpowers, I did a Q&A, discussing those topics (and more!)
Read it in the latest #ArchitectureWeekly: https://www.architecture-weekly.com/p/postgresql-partitioning-logical-replication
You'll also know what I answered for the question:
"What misuse of PostgreSQL (feature or in general) has turned out to be useful?"!
Feedback is welcome, and thanks again, @danielmarbach for the invitation!
-
“Just use #SQL”, they say.
“No need for ORMs”, they add.
And they may be right, but… But then accidental complexity piles in.
Just is enough for a simple or explicit context. Eventually, as our system grows, we’ll need to deal with complications. Popular tools might not be perfect; they may be too heavy, depending on design decisions, but as Gerald Weinberg said:
"Things are the way they are because they got that way"
You can live “just” with something. This can be a good starting point. Yet, we should always consider when deciding on DIY or “take off the shelve” solutions where we need to land and what our main problem is to solve.
Because if it appears that we’ll need more advanced features, then we’ll follow the path similar to the one that people building popular libraries/tools have taken.
It’s always worth thinking whether “just” will be enough for us. Usually, “just” is enough only for some time. And it is better not to overlook this to change our approach, as then we can deal with accidental complexity related to wrongly weighted “just”.
How does "wrongly weighted just" look like? Check in my latest #ArchitectureWeekly edition
https://www.architecture-weekly.com/p/just-use-sql-they-say-or-on-how-accidental
What are your "wrongly weighted just" horror stories?
-
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