Forum Discussion
Post ProdigyHow creating a Python custom library
Hi pmscorca,
That is correct. Here is an example of a custom workload with the extensibility toolkit: https://community.fabric.microsoft.com/t5/Extensibility-Toolkit-Gallery/Fabric-Job-Registry/m-p/5006346
Post ProdigyHi,
I need to implement and propose a solution to potential customers who have or do not have Fabric; those who don't have Fabric first will buy the solution and then Fabric.
I don't understand how a custom workload could allow to protect the code; it seems that Fabric lays everything out in plain sight.
Super Userpmscorca I know that tayloramy knows what he is saying about using Fabric custom workloads as he created them. I have yet to try it out so cannot chime on that. However, Python is Python, and as you correctly said, nothing can be hidden in Fabric once deployed. So, I just repeat, from my first-hand experience Fabric is not your answer for code protection. The fact that your solution is made specifically to run on Fabric platform should not stop your customers from purchasing it. It's similar to if someone wants to use software they need to have a computer too. Most likely your code protection is not a technical concern. Your customers agree with your terms and conditions when they decide to buy and use your solution. That said, it does not mean you should not research various ways of protecting your code, but, don't let it stop you from creating and selling your solution. That's all I have to say on this topic. If you are satisfied, feel free to give it kudos and mark as a solution. If not, keep researching and good luck.
- pmscorca
Hi, thanks for your reply.
Ok, but how protecting code might impact solution architecture.