Derek Comartin
@codeopinion
👑 Context is King 💻 Software Architecture & Design 📺 http://youtube.com/@codeopinion
คุณอาจชื่นชอบ
Random reminder that I have a YouTube channel where I post videos about software architecture and design. Usually in the 10 min range trying be concise as possible. If you enjoy please share. Have suggestions? Please let me know. youtube.com/@codeopinion
Is this serious or engagement to "subscribe to my newsletter"? I never know how to take these things anymore.
Kubernetes is overkill. Kubernetes is too complex. Almost no company needs it. These claims are destroying careers. Let me show you why learning Kubernetes now is the single best move you can make.
There is some truth to this. But lets not forget AngularJS (v1). My point is horrible tooling can be popular. Why? I still have no idea.
A trend… Use ORM, write terrible DAO layers, face problems, blame ORM. Use Java, create bad abstractions, face problems, blame Java. Use k8s, write complex configurations, face problems, blame k8s. Use Postgres, design suboptimal table structure, face problems, blame…
Ah what? I have no idea what this package is, and I'm certain I haven't uploaded it.
The thing I care most about in new .NET releases are runtime performance improvements.
We’ve all had bloated CQRS handlers. You open up a command, query, or event handler, and it’s a nightmare of code. There’s validation, authorization, state changes,etc. It’s a mess to maintain, and it’s really hard to test. Pipelines to the rescue. codeopinion.com/clean-up-bloat…
How many can you explain and unknowingly are incorrect.
As a Backend dev , how many concepts can you explain from below : 1. Event-Driven Architecture 2. Saga Pattern 3. CQRS (Command Query Responsibility Segregation) 4. Event Sourcing 5. Circuit Breaker Pattern 6. Distributed Tracing 7. CAP Theorem 8. Idempotency 9. Data…
Not shockingly this happens in the software dev world...and pretty much everything.
I go through phases where I become disillusioned with what I do Overall I’ve been at it for 20+ years and I’ve just seen people get more stupid The shit they believe gets dumber Ironically the absolute biggest morons are the most confident Honestly part of me just wants to…
I get it. Seems absurd. However if you've lived in small companies for a decent amount of time this is kinda normal.
Dear recruiters, if you are looking for: - Java, Python, PHP - React, Angular, Next - PostgreSQL, Redis, MongoDB - AWS, S3, EC2, ECS, EKS - *nix system administration - Git and CI with TDD - Docker, Kubernetes That's not a Full Stack Developer That's an entire IT department
Someone is impersonating me. If you receive a message like this on Discord or elsewhere, it is not from me. Just gross.
Double Dispatch in DDD - codeopinion.com/double-dispatc… @codeopinion
"Your domain shouldn't have any dependencies"... "it should be pure!"... Oh, the dogma. Injecting domain concepts, behaviors, and policies is probably the most domain-centric thing you could do. codeopinion.com/double-dispatc…
Working on explaining the differences between orchestration and choreography in a messaging workflow. I've tried multiple ways to describe this because, as always, there are trade-offs. Events across boundaries and compensatory actions are major factors.
47 Microservices… for 2 Requests Per Second?! A Reddit post from r/softwarearchitecture that perfectly captures the insanity and also the lack of context about scaling. But scaling what? youtu.be/OoolGJnCq4s
youtube.com
YouTube
47 Microservices… for 2 Requests Per Second?!
Application layer or domain layer — where does your authorization logic live? Great article by @codeopinion with some guidelines to keep your software architecture consistent and avoid authorization code scattered everywhere. codeopinion.com/authorization-…
You should really be able to define a filter prompt for what your feed should look like. Mine would start with " don't show me anything with 🚨 BREAKING"
Authorization, should it go in your Domain or Application Layer? It's a super common question, so here are examples and guidelines. codeopinion.com/authorization-…
*open app* "We've just raised a $50M pre-seed to help your toaster talk to your microwave." "We just raised a $230M pre-pre seed to agenticly agent your AI agents." "I'm 4 and I just dropped out of preschool to go all-in on AI -enabled candles." *close app*
No. The problem isn't orchestration. The problem is excessive coupling because of the boundaries defined.
We had microservices calling microservices calling microservices. One API request triggered 12 internal calls. Believe me, Tracing was a nightmare. Debugging took hours and hours. Adding a new service meant updating 5 other services. The problem isn't microservices. It's what…
Clients need explicit success or failure. Either use HTTP status codes or include a clear success flag and structured error in the body. Human-readable for people and machine-readable for code. By Derek Comartin at @CodeOpinion codeopinion.com/your-api-error…
United States เทรนด์
- 1. #AEWFullGear 68.4K posts
- 2. Klay 18.8K posts
- 3. Lando 93.6K posts
- 4. #LasVegasGP 177K posts
- 5. McLaren 37.6K posts
- 6. Samoa Joe 4,511 posts
- 7. LAFC 14.7K posts
- 8. gambino 1,957 posts
- 9. Swerve 6,215 posts
- 10. Hangman 9,496 posts
- 11. Ja Morant 8,110 posts
- 12. #Toonami 2,715 posts
- 13. Bryson Barnes N/A
- 14. #byucpl N/A
- 15. Max Verstappen 49.5K posts
- 16. LJ Martin 1,275 posts
- 17. Utah 23.8K posts
- 18. Benavidez 15.6K posts
- 19. Kimi 36.6K posts
- 20. Mark Briscoe 4,322 posts
คุณอาจชื่นชอบ
-
Milan Jovanović
@mjovanovictech -
Dave Callan | dotnet
@Dave_DotNet -
Andrew Lock "Sock"
@andrewlocknet -
ASP.NET Core News
@aspnetcore_news -
Nick Chapsas
@nickchapsas -
Amichai
@amantinband -
Jon P Smith
@thereformedprog -
Scott Hunter
@coolcsh -
Davide Bellone | Code4it.dev | Microsoft MVP
@BelloneDavide -
Daniel Roth
@danroth27 -
David Fowler
@davidfowl -
Zoran Horvat
@zoranh75 -
Mads Torgersen #BlackLivesStillMatter
@MadsTorgersen -
Niels Swimburger.NET 🍔
@RealSwimburger -
Gui Ferreira
@gsferreira
Something went wrong.
Something went wrong.