I came up with a thing in #fsharp today and I am unsure about it. I don't know if it's cute, useless, or useful; I cannot see far enough ahead to understand its implications.
type ErrExn = | Err of DomainError | Exn of System.Exception
This DU unifies domain errors (that are represented in a user-written DU) and exceptions.
I'd expect it to be in a function with a signature of 'a -> Result<'b, ErrExn>.
I don't know if this gives value over separate domain errors and exceptions.
@pblasucci@chethusk@greggyb
"Let it bubble up and crash" is also more in line with #kubernetes and modern #microservices 10 factor app principles.
It's not "crash" though, it is "shut down gracefully"
For a worker #process, graceful shutdown is achieved by returning the current job to the work #queue.
I've sent a little time this morning searching for articles around "patterns for service to service authentication" and found a couple of bits.
I'm trying to document/evangelise that evolution of patterns is OK (in fact preferable) to long cycle large shifts.
Anyone got any go to posts about intraService authN/authZ patterns ? I hate to say #microservices. #softwarearchitecture#devops ps
I'm looking for a tool I swear I've seen but cannot find. When running a load of #microservices locally, it caught all the Docker logs and made them nicely searchable, graphable etc without being a stinking great ElkStack. What was it? #devops#developerexperience
Whenever I post about #microservices, I get detractors pointing out problems with them, or I get people cheering them on.
I decided to write a full article explaining many of the pros and cons you should consider if you're thinking about microservices. It's a bit of a longer read, but it's an important topic that a small toot won't cover.
Though #microservices have their downsides (robustness is achieved via greater complexity), perhaps their single greatest benefit is simple. When designed well, they send and receive data. No shared memory.
That's an entire class of bugs wiped out (except inside the service, of course).
software-architektur.tv: Fishbowl: Wege für IT-Nachwuchs und Quereinsteiger
iX präsentiert Eberhard Wolffs Videocast. Diesmal live von den IT-Tagen: Eine Diskussion mit Publikum und Expertinnen und Experten über den IT-Fachkräftemangel.
If #Erlang wasn't dying out, I'd want to learn more and seek work. The world's largest telephony over ATM network ran on Erlang and had 9 nines (!) of availability. That's 31 milliseconds of downtime per year.
Part of why it was so reliable is that it's a language which basically makes you write #microservices for all functionality, but with much of the infrastructure support built in. What an amazing technology.