For more information about Brightstar DB Entity Framework attributes and passing through additional attributes, please refer to the documentation.
Step 6: Creating a context class to handle database persistence Right click on the Brightstar Entity Context and select Run Custom Tool.
Choose a name for your application (we are using Brightstar DB. Step 2: Add references to Brightstar DB Install the Brightstar DB package from Nu Get, either using the GUI tool or from the Nu Get console with the command: Step 3: Add a connection string to your Brightstar DB location Open the web.config file in the root directory your new project, and add a connection string to the location of your Brightstar DB store.
The same hashtag may appear in more than one tweet, and so the collection of Tweets is marked with the ‘Inverse Property’ attribute to show that it is the other end of the collection of Hash Tags in the ITweet interface: In order to show the speed at which objects can be created, persisted and index in Brightstar DB, the console application creates 100 users, each with 500 tweets.
Each of those tweets has 2 hashtags (chosen from a set of 10,000 hash tags).
The Tweet Box sample is a simple console application that shows the speed in which Brightstar DB can load content.
The aim is not to create a Twitter style application, but to show how objects with various relationships to one another are loading quickly, in a structure that will be familiar to developers. The relationships between the interfaces mimic the structure on Twitter, in that Users have a many to many relationship with other Users (or followers), and have a one to many relationship with Tweets.
The tweets have a many to many relationship with Hashtags, as a Tweet can have zero or more Hashtags, and a Hashtag may appear in more than one Tweet.
IUser The IUser interface represents a user on Twitter, with simple string properties for the username, bio (profile text) and date of registration.To demonstrate the ease of using Brightstar DB with ASP.NET MVC, we will use the well-known “Nerd Dinner” tutorial used by . We won’t recreate the full Nerd Dinner application, but just a portion of it, to show how to use Brightstar DB for code-first data persistence, and show how it not only matches the ease of creating applications from scratch, but surpasses Entity Framework by introducing pain free model changes (more on that later). Nerd Dinner sample application shows a simple model layer, using ASP.In order to work with simpler values for our entity Ids we decorate the Id property with an identifier attribute.This adds a prefix for Brightstar DB to use when generating and querying the entity identifiers and ensures that the actual value we get in the Id property is just the part of the URI that follows the prefix, which will be a simple GUID string.The ‘Following’ property shows the list of users that this user follows, the other end of this relationship is shown in the ‘Followers’ property, this is marked with the ‘Inverse Property’ attribute to tell Brightstar DB that Followers is the other end of the Following relationship.