Blazor Framework - Why the interest?

Blazor is a big step in modern web technology for Microsoft developers. Utilizing c# for front end development instead of javascript, it allows the back end and front end to be written in the same familiar language. It compiles and runs in native WebAssembly. This results in speed increases and reduced data transfer. Not only that, but it doesn't even need a web browser to run in, acting like its own self-running app. 

Read more: Blazor Framework - Why the interest?

Relational versus Graph Databases

Databases. Which technology to choose? There is a multitude of information out in cyberspace about how different technologies work and which would be better for any given situation.  I’d like to take some time to break down in simple terms, the difference between modeling data with a relational database and comparing to a graph database. I am not including a No-Sql or Document database in this comparison.

Let’s start with a simple scenario.  We have people, who go to a library and interact with books.

 In a relational database, everything is stored in tables (also called entities). A designer would create one table each for people, one for library and one for books. Each table has attributes (properties or columns). In the People table, you would store the name of that person. You would also have to store a unique identifier. There may be two John Smiths, so you would have to have a way to identify which John Smith you are referencing.  This unique identifier (ID) is usually handled by the database automatically, for example the first record is 1, and the next is 2 and so on.

Read more: Relational versus Graph Databases