Design Philosophy

POCO DataSet is shaped by three core design principles: lightweight structure, composability, and serialization-friendly architecture. These principles ensure that the framework remains easy to understand, extend, and integrate into modern .NET applications, particularly metadata-driven systems such as dynamic Blazor interfaces or plugin-based architectures like BPUA.

1. Lightweight

POCO DataSet intentionally avoids unnecessary complexity. It does not attempt to replicate the extensive feature set of System.Data.DataSet—such as relational graphs, constraints, typed datasets, event state machines, or XML-centric schemas. Instead, it delivers a clear and minimal foundation for representing tabular data in a predictable, uncluttered way.

• Small, focused object model: DataSet, DataTable, and DataRow.
• No dependency on heavy base classes or legacy subsystems.
• No hidden behaviors (no AcceptChanges/RejectChanges, no relation propagation).
• No automatic constraint enforcement or implicit rules.
• Minimal memory footprint with efficient internal collections.

The lightweight nature of POCO DataSet makes it easy to learn and use, reduces cognitive overhead, and avoids runtime surprises. Developers can see exactly what the system is doing—and nothing more.

2. Composable

The composable nature of POCO DataSet means that it can be combined freely with other layers, patterns, and application architectures. The library avoids imposing opinions about persistence, validation, UI, or domain modeling. Instead, it provides foundational building blocks that you can assemble into solutions tailored to your application's requirements.

• POCO interfaces such as IDataSet, IDataTable, IDataRow allow easy substitution or extension.
• Extensible ColumnMetadata enables custom attributes for rules, UI hints, or domain semantics.
• It fits naturally into dependency injection and layered architecture patterns.
• Supports plugin-based systems by allowing DataSets to be transported between independently developed modules.
• Works well with custom serialization, validation frameworks, or caching strategies.

Because the framework is composed of simple interfaces and POCO implementations, it adapts easily to both small applications and large enterprise-level systems.

3. Serialization-Friendly

POCO DataSet is designed from the ground up for safe, predictable serialization—particularly JSON. This is essential for modern web applications, distributed systems, and API-centric architectures.

• POCO objects avoid XML-era features that serialize poorly to JSON.
• Concrete type converters ensure correct reconstruction of interfaces during deserialization.
• No circular references or hidden state machines.
• Schema and data can be transported independently or together.
• Clean roundtrip behavior through System.Text.Json and Newtonsoft.Json.

Because POCO DataSet produces clean JSON structures, it integrates seamlessly with modern APIs, Blazor applications, and remote service calls without requiring custom serialization hacks or fragile workarounds.

Philosophy Summary

The design philosophy of POCO DataSet reflects a commitment to clarity, predictability, and flexibility. By being lightweight, composable, and serialization-friendly, it becomes a practical foundation for applications that need structured tabular data without the overhead and constraints of legacy systems.

These principles enable POCO DataSet to grow naturally alongside your architecture, making it a reliable, future-proof component whether you're building traditional MVC applications, API-driven backends, interactive Blazor interfaces, or complex modular systems like BPUA.

Table of Content POCO DataSet