--- title: "#nebula articles | Hashnode" description: "Explore 15 articles tagged #nebula on Hashnode. Tutorials, guides, and how-tos from the community." url: "https://hashnode.com/tag/nebula" --- Tag # #nebula 15 posts · 0 followers [Zero Heartbeat](https://hashnode.com/@clustron) · [Just now](https://hashnode.com/posts/obfuscating-a-polymorphic-json-contract-why-jsonderivedtype-survives-renaming-and-typenamehandling-d/6af8ea5a765da70cb51435a6) ### [Obfuscating a Polymorphic JSON Contract: Why \[JsonDerivedType\] Survives Renaming and TypeNameHandling Does Not](https://delta1labs.hashnode.dev/obfuscating-a-polymorphic-json-contract-why-jsonderivedtype-survives-renaming-and-typenamehandling-d?utm_source=hashnode&utm_medium=feed) Property-level renaming breaks are annoying but shallow: a key comes out wrong, you pin it with \[JsonPropertyName\], done. Polymorphic serialization is a deeper hazard, because the thing that goes on t 8 min read · [delta1labs.hashnode.dev](https://delta1labs.hashnode.dev/obfuscating-a-polymorphic-json-contract-why-jsonderivedtype-survives-renaming-and-typenamehandling-d?utm_source=hashnode&utm_medium=feed) [Zero Heartbeat](https://hashnode.com/@clustron) · [2h ago](https://hashnode.com/posts/obfuscating-a-semantic-kernel-plugin-what-the-model-reads-and-what-you-can-harden/6af8c0853a61f556217637df) ### [Obfuscating a Semantic Kernel Plugin: What the Model Reads, and What You Can Harden](https://delta1labs.hashnode.dev/obfuscating-a-semantic-kernel-plugin-what-the-model-reads-and-what-you-can-harden?utm_source=hashnode&utm_medium=feed) Most "do not obfuscate this" advice is about serialization: a member name is also the wire key, so renaming it breaks the contract. A Semantic Kernel plugin is the same story wearing new clothes. You 9 min read · [delta1labs.hashnode.dev](https://delta1labs.hashnode.dev/obfuscating-a-semantic-kernel-plugin-what-the-model-reads-and-what-you-can-harden?utm_source=hashnode&utm_medium=feed) [Zero Heartbeat](https://hashnode.com/@clustron) · [6h ago](https://hashnode.com/posts/obfuscating-a-refit-rest-client-what-the-interface-attributes-pin-and-what-you-can-safely-rename/6af8928c4aebfdfe7ae18adf) ### [Obfuscating a Refit REST Client: What the Interface Attributes Pin, and What You Can Safely Rename](https://delta1labs.hashnode.dev/obfuscating-a-refit-rest-client-what-the-interface-attributes-pin-and-what-you-can-safely-rename?utm_source=hashnode&utm_medium=feed) Most "do not obfuscate this" warnings are about serialization: the member name is the wire key, so renaming breaks it. Refit looks like it should be in that category — you hand it a C# interface and i 7 min read · [delta1labs.hashnode.dev](https://delta1labs.hashnode.dev/obfuscating-a-refit-rest-client-what-the-interface-attributes-pin-and-what-you-can-safely-rename?utm_source=hashnode&utm_medium=feed) [Zero Heartbeat](https://hashnode.com/@clustron) · [18h ago](https://hashnode.com/posts/obfuscating-a-protobuf-net-app-why-numeric-field-tags-make-it-rename-friendly/6af7ed000c58cec585ad990d) ### [Obfuscating a protobuf-net App: Why Numeric Field Tags Make It Rename-Friendly](https://delta1labs.hashnode.dev/obfuscating-a-protobuf-net-app-why-numeric-field-tags-make-it-rename-friendly?utm_source=hashnode&utm_medium=feed) Most advice about obfuscating serialized types is a warning: do not rename your DTOs, the names are the contract. That is correct for System.Text.Json, Newtonsoft.Json, and DataContract/WCF — the memb 8 min read · [delta1labs.hashnode.dev](https://delta1labs.hashnode.dev/obfuscating-a-protobuf-net-app-why-numeric-field-tags-make-it-rename-friendly?utm_source=hashnode&utm_medium=feed) [Zero Heartbeat](https://hashnode.com/@clustron) · [21h ago](https://hashnode.com/posts/obfuscating-a-wcf-service-without-breaking-the-wire-contract/6af7c30becb2109c71010956) ### [Obfuscating a WCF service without breaking the wire contract](https://delta1labs.hashnode.dev/obfuscating-a-wcf-service-without-breaking-the-wire-contract?utm_source=hashnode&utm_medium=feed) A WCF service is one of the harder things to obfuscate safely, and the reason is subtle: the obfuscator and the serializer both care about your member names, but for opposite reasons. Nebula wants to 7 min read · [delta1labs.hashnode.dev](https://delta1labs.hashnode.dev/obfuscating-a-wcf-service-without-breaking-the-wire-contract?utm_source=hashnode&utm_medium=feed) [Zero Heartbeat](https://hashnode.com/@clustron) · [23h ago](https://hashnode.com/posts/obfuscating-a-masstransit-app-without-breaking-message-routing/6af7995a4d4f1dd0e251dfb6) ### [Obfuscating a MassTransit App Without Breaking Message Routing](https://delta1labs.hashnode.dev/obfuscating-a-masstransit-app-without-breaking-message-routing?utm_source=hashnode&utm_medium=feed) A MassTransit application is a tempting obfuscation target: consumers, sagas and routing-slip activities are where your business logic lives, and most of it can be renamed, string-encrypted and virtua 14 min read · [delta1labs.hashnode.dev](https://delta1labs.hashnode.dev/obfuscating-a-masstransit-app-without-breaking-message-routing?utm_source=hashnode&utm_medium=feed) [Zero Heartbeat](https://hashnode.com/@clustron) · [1d ago](https://hashnode.com/posts/obfuscating-a-dapper-data-access-layer-without-breaking-column-to-property-mapping/6af76eac3c4ecabfae838103) ### [Obfuscating a Dapper data-access layer without breaking column-to-property mapping](https://delta1labs.hashnode.dev/obfuscating-a-dapper-data-access-layer-without-breaking-column-to-property-mapping?utm_source=hashnode&utm_medium=feed) A micro-ORM like Dapper earns its speed by doing very little magic, but the one piece of magic it does keep is the piece that collides with obfuscation. When you write connection.Query("SELE 12 min read · [delta1labs.hashnode.dev](https://delta1labs.hashnode.dev/obfuscating-a-dapper-data-access-layer-without-breaking-column-to-property-mapping?utm_source=hashnode&utm_medium=feed) [Zero Heartbeat](https://hashnode.com/@clustron) · [1d ago](https://hashnode.com/posts/obfuscating-a-hangfire-app-without-breaking-persisted-background-jobs/6af744b2edaa2d2ee5787348) ### [Obfuscating a Hangfire App Without Breaking Persisted Background Jobs](https://delta1labs.hashnode.dev/obfuscating-a-hangfire-app-without-breaking-persisted-background-jobs?utm_source=hashnode&utm_medium=feed) A Hangfire application looks like an easy obfuscation target. The job classes are plumbing; the valuable code is what they call into. But Hangfire has one seam that a naive obfuscation pass walks stra 12 min read · [delta1labs.hashnode.dev](https://delta1labs.hashnode.dev/obfuscating-a-hangfire-app-without-breaking-persisted-background-jobs?utm_source=hashnode&utm_medium=feed) [Zero Heartbeat](https://hashnode.com/@clustron) · [1d ago](https://hashnode.com/posts/obfuscating-strongly-typed-configuration-without-breaking-ioptionst-binding/6af71c549e0edbe117b6efc0) ### [Obfuscating strongly-typed configuration without breaking IOptions binding](https://delta1labs.hashnode.dev/obfuscating-strongly-typed-configuration-without-breaking-ioptionst-binding?utm_source=hashnode&utm_medium=feed) A strongly-typed options class looks like the most ordinary C# in your solution — a POCO with public properties and nothing clever about it. But the moment you pass it to services.Configure, a few 10 min read · [delta1labs.hashnode.dev](https://delta1labs.hashnode.dev/obfuscating-strongly-typed-configuration-without-breaking-ioptionst-binding?utm_source=hashnode&utm_medium=feed) [Zero Heartbeat](https://hashnode.com/@clustron) · [1d ago](https://hashnode.com/posts/obfuscating-a-net-aws-lambda-function-without-breaking-the-handler-string/6af6f02344c2a13c76df2a90) ### [Obfuscating a .NET AWS Lambda Function Without Breaking the Handler String](https://delta1labs.hashnode.dev/obfuscating-a-net-aws-lambda-function-without-breaking-the-handler-string?utm_source=hashnode&utm_medium=feed) A .NET AWS Lambda function is close to the ideal obfuscation target. It is a small class library — no Main in the managed case, no UI, one method that Lambda calls — that ships to infrastructure you d 12 min read · [delta1labs.hashnode.dev](https://delta1labs.hashnode.dev/obfuscating-a-net-aws-lambda-function-without-breaking-the-handler-string?utm_source=hashnode&utm_medium=feed)