Discover and read the best of Twitter Threads about #CQRS
Most recents (5)
🚀 Backend Developer Roadmap for .NET Developers. (2023 Edition)
Follow this thread along for the entire roadmap.
#dotnet #developer #backend
Follow this thread along for the entire roadmap.
#dotnet #developer #backend
Step 0: Know your basics.
Be familiar with OOPS, Brush up your problem solving skills, and learn GIT.
#dotnet #developer #backend
Be familiar with OOPS, Brush up your problem solving skills, and learn GIT.
#dotnet #developer #backend
In recent days I saw several examples of "actions" in #Laravel, but one especially got my attention and I wanted to clarify it - so we had little discussion with @wendell_adriel and I would like to share my opinion about this particular approach 🙂
🧵👇
🧵👇
Before we start, one important preface: I'm big fan of explicitness and testability, so I'm using dependency injection everywhere (where's applicable). Examples in this thread will use it too by default, along with #PHP 8.0+ syntaxes.
What caught my attention was instantiating action inside controller's method 🤔 That looked suspicious, because I'm used to different nomenclature.
My assumption after looking at the example was that `CreateUserAction` is more like a #CQRS command rather than action.
My assumption after looking at the example was that `CreateUserAction` is more like a #CQRS command rather than action.
The first time I built a CQRS system… it was in 2006. The term hadn’t be coined yet by Greg (that happened in 2010), but the practice was ubiquitous in finance with tons of high throughput platforms to build or to maintain.
Actually, the first time I’ve used this architecture style was not due to my young skills of tech architect, but rather on a technical constraint.
Bir yazılım geliştiricinin bilmesi gerekenlerle ilgili 15 maddelik flood geliyor.. Mümkün olduğunca fazla keywordü bir araya toplamaya çalıştım.
Hadi Başlıyoruz!
#Developer #Software #Java #code #kod #yazılım #development #computer #bilgisayar #tool #PC #IT #web #tech #data
Hadi Başlıyoruz!
#Developer #Software #Java #code #kod #yazılım #development #computer #bilgisayar #tool #PC #IT #web #tech #data
1-Temel veri yapıları (linkedList, map, tree vb) ve temel algoritmalar (sıralama, arama vb)
Sıfırdan kodlama ihtiyacınız büyük ihtimalle hiç olmayacak. Ancak ihtiyaç anında doğru yerde doğrusunu seçebilmek için o veri yapısının veya algoritmanın nasıl çalıştığını bilmeniz şart
Sıfırdan kodlama ihtiyacınız büyük ihtimalle hiç olmayacak. Ancak ihtiyaç anında doğru yerde doğrusunu seçebilmek için o veri yapısının veya algoritmanın nasıl çalıştığını bilmeniz şart
I feel very sad about this, but I am compelled to comment. This article does such a great disservice to #DDDesign #CQRS and #EventSourcing that if my platform/toolkit/framework where cited in it, I'd demand removal:
The software industry is continuously exposed to such poor literature and guidance. The term "domain model" should not even be used here, nor "domain event." Even so, the whole article is flawed. Please don't follow this advice.
Unfortunately this article argues "accidental complexity" as a reason to change the "domain model" and then goes about introducing heaps of unnecessary complexity. This appears to be an effort in showcasing a framework rather than simplifying the solution.
