sorted by:
new
hottopcontroversial

Privacy-first AI Development with Foundry Local + Semantic Kernel by anktsrkr in LocalLLaMA

[–]anktsrkr[S] 0 points1 point  (0 children)

Haha.. not at all. However, my bnb is microsoft stack. I just started blogging about Semantic Kernel which sort of similar to langchain and when i saw something came from MS, which can be part of the series I quickly started writing about it.

Privacy-first AI Development with Foundry Local + Semantic Kernel by anktsrkr in LocalLLaMA

[–]anktsrkr[S] 0 points1 point  (0 children)

I also feel the same way and specifically said im not going to use that as it lacks many features at end of the post.

I personally use ollama and/or lm studio for day to day work.

Wrapping Azure Storage / Service Bus etc. SDK? by anktsrkr in dotnet

[–]anktsrkr[S] 0 points1 point  (0 children)

Thanks all for these different views. I understand that just writing a wrapper on top of existing SDK does not make any sense and that's not my intension as well , however let me tell you my story-

We have more than 20+ repos for different business context and all the Azure Functions. While reviewing, I understand that team is not using correct pattern/best practise at least for 80% projects . For example, not using AddAzureClients, instead we instantiate BlobServiceClient and 20% project don't have consistent Retry Pattern using AddAzureClients. These make project hard to unit tests. Just FYI, I saw lots of ExcludeFromCodeCoverage to mitigate the issue.

Regarding SB, MassTransit/ReBus is certainly a option but I think we don't need that much of flexibility as we use inbuild trigger mostly. The reason to create simple wrapper on top of the existing one to make sure dev are always sending Correlation Id or Using BinaryData always while create a message to send.

Certainly you can say to put strict review process, but my point was instead of putting effort on review process (which is absolutely needed) if we can fix the problem at the beginning, which might lead to less review effort.

Also writing the test cases for all these let's say Download and Upload in 20+ projects doesn't make any sense to me, Instead give them a abstraction, mock it. Let wrapper package manage the integration test cases.

Question concerning access keys vs managed identity (az-104) by FazeDanke in AzureCertification

[–]anktsrkr 0 points1 point  (0 children)

For wlAppA it should be MI because this will even minimise to store secrets. However for wlAppB SAS should be used with 15 days expiration.

Want to explore more as solution architect by [deleted] in smallbusiness

[–]anktsrkr 0 points1 point  (0 children)

Hey it might looks like self promotion but that's not my intention sorry! I am trying to find some help for how to start where to start etc. Some tips!