Learning over the holidays: Yet Another Bug Tracker sample app
If you are reading this blog, I assume that you are a like-minded person. My idea of relaxation is to sit and write code. Hopefully on something that I’m not familiar with. I have many such blog post series covering topics I care about. It’s my idea of meditation.
For the end of 2023, I thought that we could do something similar but on a broader scale. A while ago Alex Klaus wrote a walkthrough on how to build a complete application from scratch using modern best practices (and RavenDB). We refreshed the code and made it widely available, offering you something fun , educational, and productive to engage with.
The system is a bug tracker (allowing us to focus on the architecture rather than domain concerns), and you can play with a deployed version live. The code is available under the MIT license, and we’ll be very happy to receive any suggested improvements.
Topics that are covered:
Building an enterprise application with the .NET and RavenDB
Non-Relational Data Modeling Through Domain Driven Design Prism
Entity Relationships in non-relational database (one-to-many, many-to-many)
As usual, I would love any feedback you have to offer.
Comments
interesting to show int his example how manage the notion of the unique constraints
what if I want to run RavenDB in a not distribuite cluster and I would like to opt for set up unique constraint feature?
see... https://ayende.com/blog/180066/unique-constraints-didnt-make-the-cut-for-ravendb-4-0
Mario,
We have cluster wide transactions for that purpose, if you need them. Or just optimistic concurrency if you have one node.
I would like to opt for set up unique constraint , is it possible?
Mario, Can you post the full details on your scenarios here: https://github.com/ravendb/ravendb/discussions/
That would make it easier to discuss
Comment preview