Search
175 results for “oskardudycz”
-
This week, a surprising thing happened to me. In #ArchitectureWeekly, I try to share my perspective experience every week, but I don't like acting as an expert. That's why I am inviting special guests who know specific areas much better than I do. Sometimes, there are webinars, sometimes podcast-like interviews. What's the surprising part?
In this week's episode with @hazelweakly we discussed observability, and Hazel made us switch places, and she started interviewing me
1/
-
Plus, #Emmett got 200 GitHub stars. Nice milestone!
Next week, next milestone, as I'll be running the first private workshop about Event Sourcing with #Emmett!
If you're interested in using or contributing to #Emmett, join our Discord: https://discord.gg/fTpqUTMmVa
3/
-
#EventSourcing in #NodeJs just got better with new #Emmett features!
#PostgreSQL event store now has the first version of async subscriptions notifying about appended events. Thanks to that, you can now handle asynchronous workflows, integrations and projections. It's still experimental, but it works. See: https://github.com/event-driven-io/emmett/pull/128
1/
-
Super happy that next week I'll be running a first internal paid workshop about #Emmett! 🥳
-
That's why I'm happy that @hazelweakly agreed to record the #ArchitectureWeekly podcast episode and try to bridge those two perspectives.
https://www.architecture-weekly.com/p/applying-observability-from-strategy
@hazelweakly is one of the best people in the observability space. I think that she doesn't need an introduction here as one of the persons who made the Hachyderm instance operable, safe, and community-driven.
That's also where we started the episode, but we went much further! Also beyond the #OpenTelemetry
2/
-
I’ll give you two numbers: 15 and 47. What are them? 15 is the number of hours left to get a 30-day FREE trial to all #ArchitectureWeekly content.
47 is the number of people decided to give it a go!
So don’t wait, click here: https://www.architecture-weekly.com/blackfriday2024
Read all articles, watch over 40h of video learning materials and decide whether you stay longer or just benefit from free knowledge!
If you like it, share with your friends so they can also benefit! 🙂❤️
-
If you like #TypeScript VooDoo, I had to add some to #Emmett. Warning: content for #TypeScript connoisseurs!
-
Is today a #BlackFriday? Yes, it is! Are you looking for decent content about #SoftwareArchitecture? Yes, you do! Do I have something for you? Yes, I do!
You can get a 30-day free trial of my #ArchitectureWeekly newsletter by going to this magic link: https://www.architecture-weekly.com/blackfriday2024
You can get access to all paid content, articles, and over 40 hours of video recording. Try it and decide if you want to stay.
👋 Feel invited to join!
The offer lasts till the end of the week, so be quick!
-
Have you considered applying observability but struggled to match the strategy with the tooling? Or maybe you were lost on how to do it? I have something for you, or actually a sneak peek of what we'll be in next Monday's #ArchitectureWeekly edition!
I had a great discussion with @hazelweakly about Observability beyond Open Telemetry, keeping it "meaty" with practical thoughts. I learned a lot, and I'm sure you will, too!
Subscribe and don't miss it: https://www.architecture-weekly.com/blackfriday2024! 😀
-
In the latest #ArchitectureWeekly, I discussed deduplication strategies, assessed their usefulness, and considered scenarios where you may need them. I also did a reality check on messaging vendors' promises of exactly-once delivery.
TLDR: They're broken.
https://www.architecture-weekly.com/p/deduplication-in-distributed-systems
And hey, this is a free edition post, so no paywall this time! 😀 Fasten your seat belts, and grab a coffee, as this is a long read.
Are you using deduplication in your messaging systems?
-
This article took me a time to prepare, so feedback is more than welcomed!
https://event-driven.io/en/idempotent_command_handling/
p.s. And guess what? Most of that is already available in #Emmett 👌😎
3/3
-
@smallcircles I was thinking about some dual license, but I think I’ll go with AGPL after hearing recent @changelog podcast episode about ElasticSearch changing back to it kinda persuaded me https://changelog.com/topic/elasticsearch
Might be that there will be some closed source or source available products around #Emmett but to make it explicit about intention and liabilities.
-
In my recent article the leitmotif is how to bootstrap CRUD applications with #Pongo.
If you’re not considering using my tool, or Node.js in general, then I believe it could be useful for the second hidden plot.
This practical example was a chance for me to discuss what’s actually CRUD for me. When it’s fine to use it, when not.
I also touched on how it relates to CQRS.
Yes, I believe that you can do CRUD and CQRS at the same time. How come? Read more 👇
https://event-driven.io/en/crud_with_pongo/2/2
-
I'm being quite frank about my desire to make working on #Emmett, #Pongo, and other community projects sustainable. I'd like to get enough money from direct work on those projects to fully focus on them and bring more value to you and your projects.
I think that supporting #OpenSource is a win-win for both sides. If you're using or considering using Emmett or Pongo tools, it's also some sort of due diligence to reduce the bus factor and maintain them continuously.
1/
-
I might never reach full compatibility, as the API can have numerous permutations that I didn't predict. I don't want to block anyone waiting for the new release with the fix. I think that SQL is a decent fallback.
That's why I added a few options for using #SQL in the #Pongo API.
Read more about them in my recent article 👇
https://event-driven.io/en/sql_support_in_pongo/
What are your thoughts?
4/4
-
Users should get a learning ladder. That's why I optimise the API and tooling for the newbies.
That's why, in #Pongo, I'm trying to join two accessibilities: muscle memory and the Node.js community by reusing the #MongoDB client API and #PostgreSQL operation easiness and familiarity. I think that enables me to ramp up quickly and deliver business value by deploying the first version of your software to production.
2/
-
In case you missed it, I gathered some thoughts on how, why I’ve built #Pongo, a #Mongodb #NodeJs alternative written with #TypeScript
-
I had a lot of fun showcasing and explaining #Pongo with @FranckPachot on the #YugabyteDB stream.
We went together to discuss why #Pongo uses #PostgreSQL. Seeing live how that plays with #nodejs and #typescript
We also saw some SQL and explained how JSONB storage works, among many other things.
Check it out here: https://www.youtube.com/watch?v=p-6fpV_GDEs
Leave the feedback afterwards.
Boosting is also appreciated!
-
I think that I made a good progress on #Pongo shell improvements.
Pongo is my #Nodejs project that allows the use of #PostgreSQL as a document database with # Mongo-compliant syntax.
I think that having a shell gives a good experience, allowing you to just play with tools.
Just try it with:
npx @event-driven-io/pongo@latest shellHere's how it looks 👇
Check Pongo more here: https://github.com/event-driven-io/Pongo
-
If you'd like to see what I'm brewing with #Pongo, so using PostgreSQL as a strongly-consistent Document Database in #nodejs and #typescript, check the video https://www.youtube.com/live/P4r19rv4vOg
There were some bloopers during live coding, presentation gods weren't with me today, but I think it's still a decent mark of the #Pongo journey 😉
-
I just noticed we're one person short of having 100 people on the #Emmett & #Pongo Discord server.
Who wants to be the 100th? 😀
Feel invited! https://discord.com/invite/VzvxR5Rb38
-
Boom 💣💥 New #Pongo Release with a huge set of changes!
1. New Pongo shell, you can now use REPL without installing Pongo in your project.
2. Optimistic Concurrency handling, no need for Mongo-like retries.
3. You can use custom SQL updates, filtering with useful SQL tagged template literals to cover what's missing in the API,
4. You can now print your queries to the console to track what's happening
5. Added sample using hashtag#CockroachDB and typed client.
-
As I'm working on adding observability #Emmett and #Pongo, I decided to return to this idea and show how tests can drive predictable observability!
Check the latest #ArchitectureWeekly release to see my take: https://www.architecture-weekly.com/p/making-your-system-observability
As always, feedback is more than welcome!
4/4
-
I need your brain! Today, I started working on the Emmett CLI and Config file structures.
I want Emmett to be able to generate the schema upfront for event store and read models. I also want to make a first step towards plugin infrastructure and modularity.
Check the sample config file. It'll contain plugins (similar to eslint, etc.) so each Emmett package can self-register, and community plugins can be registered in the future.
-
In case you missed it, #Pongo got a big release with a new feature set yesterday.
I know that reading release notes may sound boring, so I did a more human-readable write-up, especially for you.
https://event-driven.io/en/pongo_strongly_typed_client/
I covered why getting a strongly typed client with full typing and storage migrations is a big deal in both DevEx and Performance.
p.s. Pongo is like a Mongo but uses Postgres to give you strong consistency and user-friendly API. Check it out
-
New big 🐶 #Pongo release!
💪 Strongly typed client.
You can define your collections typed schema and benefit from Typescript. It'll automatically generate the collections with provided names and typing.
🖥️ CLI tool
Together with typed schema, enables running database migrations upfront. That helps to get a performance boost, as you can disable automated schema setup (which is good for the dev environment but not for the prod).
See: https://github.com/event-driven-io/Pongo/releases/tag/0.14.0
-
It's been a week since the initial 🐶 #Pongo release, and I have a big set of updates!
1. I managed to close the basic coverage of document manipulation methods. I added initial versions of what was initially missing: replaceOne, drop, rename, countDocuments, count, estimatedDocumentCount, findOneAndDelete, findOneAndReplace, findOneAndUpdate, etc.
1/