jbogard
Re:Performance Improvements in .NET 6
on Friday August 20, 2021 @05:40PM (#28251718)
IdentityServer is still Apache 2.0, that has not changed.
Re:Performance Improvements in .NET 6
on Friday August 20, 2021 @05:39PM (#28251713)
IdentityServer is not closed source, it is still Apache 2.0.
Re:What ORMs have taught me: just learn SQL (2014)
on Friday September 20, 2019 @09:00PM (#21032787)
Just learn both? Use ORM for writes, SQL for reads, if you need to. ORMs do not obviate the need to learn SQL.
Re:Sweden's cashless society is no longer a utopia
on Saturday November 10, 2018 @07:00PM (#18424214)
Just fine. I haven’t carried cash in Scandinavia, or Europe, for years now. It’s really not any big deal, just use your check card like you would in the states.
In fact, it’s easier now. Before chip and now contactless was ubiquitous like it is now, I got all the krone mixed up. Traveling back and forth from Copenhagen and Malmo with cash was the worst. Couldn’t tell the difference but the locals absolutely could!
Re:Sqlite: Code Of Conduct
on Monday October 22, 2018 @12:40PM (#18276134)
This is now the dumbest CoC I've seen today, and the RMS one set quite the low bar. Any actual enforceable CoC that may get adopted loses any credibility with this move.
Re:Building a CQRS/ES web application in Elixir using Phoenix
on Monday January 09, 2017 @03:24PM (#13359476)
Not production ready - the system, not the database. We never had a problem with the event data stores. The bespoke systems our CQRS/ES rescuees built around it, absolutely.
Re:Building a CQRS/ES web application in Elixir using Phoenix
on Friday January 06, 2017 @05:35PM (#13340933)
Oh yeah, us too. We use CQRS on nearly all projects we do these days. But event sourcing, totally different animal.
Re:Building a CQRS/ES web application in Elixir using Phoenix
on Friday January 06, 2017 @05:22PM (#13340855)
Wow, this succinctly sums up our experience. Fun to develop against, absolute nightmare to support in production.
The only place I'd recommend it these days are where the business views their state as an event stream, maybe finance/stocks. Not developer-forced-events like "customer address updated" or "user email changed".
Even workflow systems I've dealt with, the business doesn't view their state as an event stream. The state is where it is, how it got there is an interesting footnote.