Thursday, September 24, 2015

Three pipes to the database


Supports Windows authentication, mixed, role-based, as well as custom security for individual users.

Deep linking/nesting is not supported for security reasons and to create a conceptual separation between database and application.  A 'stored procedure set' vs. table-mapping.

Monday, September 14, 2015

Data access in THREE lines of code

Email me for the link (with source code) Persistence.dll should be self-explanatory.

Any database. Any language. (Currently written for C#/SQL Server)

Wednesday, June 24, 2015

Imagine you are James Bond's wife.

And James Bond goes missing and you want to review his assignment records and last known whereabouts.  But you need to verify the computer data can be trusted.  As you are probably not a database or computer expert, you'd have to be able to review quickly, with or without assistance.

That is why code needs to be clear, concise, and human-readable.  Secondly, you need to know who the database expert is before the mission.

Saturday, June 20, 2015

What does System.Persistence do?

System.Persistence is an "engine" that sits between the database and the software, translating all data back and forth between.  Since all data goes through that "engine", it allows full security and logging.

The code is readable by non-technical people (with some training) so non-technical people can be certain that the system is indeed secure.

Aside from its security, the system works with any application and makes software easier to write and easier to maintain.  Existing systems can be re-written incrementally using the best-practices in System.Persistence with no downtime.

System.Persistence forces best-practices in n-tier software design, and makes it easy to follow with code-generation that is fully customizable.

Note:  the current version is designed for SQL Server and .NET, but it will also work with any database in any language.

Tuesday, June 16, 2015

Three points on security

1. All data-access goes through stored procedures.
2. Log every database "hit" to the individual user, if desired.
3. A single DBA manages security for the database and is publicly accountable.

Wednesday, January 28, 2015

Basic performance numbers

Single loads:  4 ms per object (30 properties/columns/fields).
Lists:  200 ms per 1000 objects.