gmanvel.bsky.social
28 posts
64 followers
158 following
Regular Contributor
Active Commenter
comment in response to
post
Thanks for sharing ! I loved these posts showing how business world differs from software world.
udidahan.com/2010/08/31/r...
comment in response to
post
Exactly my point I was sharing internally yesterday
comment in response to
post
So this is part of Azure Service SDK ? What about scenario when message handlers need to appear under the “span” that sent the message ? E.g. service A sends bunch of messages to be processed and Service B processes these messages. Wouldn’t this help to group these spans under the parent ?
comment in response to
post
While all of them are interesting, I’d pick setting up to move modules out later & orchestration/choreography between logical modules. I think first one is important given pace of change and need to adapt. Second, I’d love to see how logical module boundaries are defined & integrated.
comment in response to
post
Curious how those modules came to be ? Are they themselves bounded context(s)? What’s the decomposition principle?
comment in response to
post
My mental model of a service is “technical authority over business capability” (SOA). Microservices then break it down to smaller autonomous parts. So quite often they end up being process view.
comment in response to
post
So in a way you’re saying that microservice is a logical boundary, which physically could be broken down to smaller pieces (kafka consumer, ETL process etc) ?
comment in response to
post
Tbh I was always surprised how espn keeps him as an analyst/commentator. No wonder a lot of people were calling him names (for his “professional” opinions). Now this… smh
comment in response to
post
Would you mind sharing few of those challenges ?
comment in response to
post
Holiday in Poland, could catch up with some „watch later” NDC talks (including your practical observability in .net 🔭 )
comment in response to
post
I cover this topic in my workshop, next one will be at #ndclondon and #ndcoslo 😜
ndclondon.com/workshops/de...
comment in response to
post
Btw I’m also hoping to find insights/tools to help breaking down business model to capabilities which hopefully will help with discovering service boundaries in SOA.
comment in response to
post
I do, although I’m nowhere near CIO role, I was always curious how business goals/strategy gets translated to tech strategy & gets executed/delivered. So far I find the content relevant.
comment in response to
post
The Accidental CIO 🤷♂️
comment in response to
post
Reason to go crazy - ofc not, raise a concern and post for discussion - sure. I think killing VS support for Mac took many by surprise, so it’s nothing unheard of from Microsoft.
(I’m not talking about content of comments, just the post itself)
comment in response to
post
One tool that I was using for apps that are already in Azure - blob leases - learn.microsoft.com/en-us/rest/a...
Not to mention some azure services use it implicitly (for example azure functions when using [Singleton] mode)
comment in response to
post
that is worse than VS, w/o a clear msg on plans to improve .net (c#) dev experience.
comment in response to
post
Yeph, I’m 100 % with you on this, outside of .net (c#) context it does make sense to make it a flagship product given its user base. But the discussion started with r/dotnet post, which are .net peeps concerned that they might be forced to use tool…
comment in response to
post
C# is not everything (& I appreciate your vast contributions to F# support in VSCode), but as you said it’s most adapted. So I think “VSCode can replace VS as a flagship product” might trigger some concerned discussions.
comment in response to
post
Well “dudes” are from .NET space where dev experience is better in VS than VS Code for non trivial tasks. And that _someone_ who made the “flagship” product remark is a GitHub dev advocate & frequent speaker/active voice in the community, so the concerns they’re raising feels legitimate.
comment in response to
post
I could see small teams (2-3 teams) using common libs, which implement cross cutting concerns (security, documentation, observability), with great success. Wouldn't you want unified approach across (small) teams in implementing these? I understand once you scale (Amazon) the game is different.
comment in response to
post
Using generic/common libs/frameworks - in my experience I'd say depends on the scale. I've seen a case when company wide swiss army lib was created and enforced to be used (logging, security, base controllers etc) & it failed just like you described. In another case...
comment in response to
post
@oskardudycz.bsky.social thanks for detailed thread, I appreciate it ! I totally agree with CI/CD part, best DevOps team I ever worked with was following this approach - creating shared templates & letting each team to build their own pipelines using the templates, extending when necessary.
comment in response to
post
What would be a good, illustrative example of tech tool vs tech focused platform ? So to say instead of using X tech focused platform better to have Y tech tool.
comment in response to
post
Thanks for sharing. This is really interesting ! It’s unfortunate I didn’t know about this lib until recently, the “Why Brighter?” really resonated with me!
comment in response to
post
Are you planning a more detailed write up (blog) about these changes ? Maybe you could share links to GitHub discussions/PRs?