dolittle/bifrost

This is the stable release of Dolittle till its out of alpha->beta stages

IMPORTANT: WE'VE MOVED TO HERE

Source	Version
NuGet
MyGet

Platform	Build Status
Windows
Linux

Documentation can be found here

You can find the CI package feed here

Bifrost is a platform designed to build Line of Business applications without sacrificing architectural quality, code quality or scalability. Embracing the concepts of Domain Driven Design, it helps developers and other stakeholders focus on business need and business value, rather than on the more technical aspects of the solution. Built from the ground up, it both embodies as well as encourages best quality engineering practises such as the SOLID principles, Convention Over Configuration and Separation of Concerns. Utilising CQRS, it fits perfectly with the ideas and promises of microservices and promotes the paradigm shift in thinking that can take LOB applications to the Cloud.

Sponsors

Site

For more details, samples, documentation, please go to the official site

Contributing

Learn how you can contribute here

bifrost's Issues

Fix pubsub mechanism for messages in namespaces

CommandMetaData for adding data to Commands that does not appear in the clients that issue commands

In many cases you need to have additional information related to a command that does not exist in the client or the client should not be responsible for, for instance if you have a shopping cart and you want to add an item to it and you want it to be added with the current price of the product but don't want the price to come from the client as it can be tampered with. CommandMetaData could then fill this gap.

Bifrost should automatically pick up any classes implementing CommandMetaDataDescriptor or similar for the specific command and make sure it populates the meta-data on the command.

Look at performance issues related to event subscribers

More specifically the MergeSubscribersFromRepository() method on EventSubscriptionManager is called often and has a substantial performance impact

Add support for getting an entity by its Id in EntityContext

Add .Get() method that takes an object as the key. The different implementations should throw an exception if the particular object type is not defined with a key or it has a composite key and it is not able to resolve the key from the single object going in.

Any internal implementations using .Any() or .Where(e => e.Id == id) or similar on the Entities queryable should be optimized to use this new approach.

Investigate the possibility to let RavenDb sessions live per request (or default scope for the container)

Chapter transition validation

Ref discussion at the forums: https://groups.google.com/d/topic/bifrostproject/FemNljyt5Rc/discussion

As a part of pushing sagas forward, a chapter needs some sense of where it's transitioning to / from.

Recursively gather validation data from members/properties without validators directly

When gathering MetaData for validation, today the gathering is only being done on first-level, not recursing through the properties. Some properties might not have validator rules directly on them, but have validators associated with them that has rules on second level properties and so forth..

Implement support for StructureMap container

View.Get() can crash if it is not finding any

The implementation is using a cast after SingleOrDefault().

Look at casting during select instead :

    public T Get(Guid id)
    {
        if( typeof(T).HasInterface<IHaveId>() )
        {
            var queryable = (IQueryable<IHaveId>)Query;
            var instance = (from o in queryable
                            where o.Id == id
                            select o).SingleOrDefault();
            return (T)instance;
        }

        throw new ObjectDoesNotHaveIdException();
    }

    public T Get(Guid id)
    {
        if( typeof(T).HasInterface<IHaveId>() )
        {
            var queryable = (IQueryable<IHaveId>)Query;
            var instance = (from o in queryable
                            where o.Id == id
                            select (T)o)  // LARS: note the addition of (T) cast here
                            .SingleOrDefault();

            return instance;  // LARS: (T) cast not necessary here anymore
        }

        throw new ObjectDoesNotHaveIdException();
    }

Update CQRS documentation to reflect todays truth!

AggregateRootRepository should have support for a method called Exists()

Implement Execution Context

A way to hold meta data that will be attached to Commands and Events. This MetaData can typically contain tenant information and in a Web context is built on a per request basis. The MetaData is considered cross cutting through all concerns and can be read out by every aspect of the system, but only assigned by its owning application (IApplication)

Support different formats depending on the content-type

Today we only support JSON in and out of services, I think it would be helpful if we could add XML and also investigate into supporting ProtoBuf

• http://code.google.com/p/protobuf-net/
• http://code.google.com/p/protobuf-js/
• http://github.com/sirikata/protojs

The reasoning behind protocol buffer support is for decreasing the bandwidth used in transferring data back and forth for a client. I think a good idea here would be to have a general service layer that can be configured for what content type to use by default. This basically to improve on developer experience during development. Its easier to look at a JSON response than a protocol buffer one. :)

Support validation of objects - not only members

Change Id on Event to be sequential

Affects for now NHibernate and any other implementations that has a specific mapping towards its datasource

Global loading hookup for when the page is loading - "application startup"

The hookup should support a way to create a start page that loads it all - the entry point of any applications.

Finish the Mongo support

The mongo entitycontext is missing some functionality, like Delete.

Also, you can only retrieve all entities of a type at once, while it might have been nice to be able to use mongo specific features like findOne().

Implement a non embeddable version of RavenDb

Support validation of objects - not only members

• Object should be extended with isValid() observable property, aggregating on members and represent object validation state.
• Object level rules

SEO : Serverside "rendering" of Single Page Applications

For search engine crawlers that are not capable of executing the JavaScripts needed to render the composed page we need to execute the JavaScripts on the server - basically use something like Env.js and just throw it same URL and let it render everything and then spit out the HTML as a result.

One thing that is very important to make note of is that we need to be able to know when the composition is done - so Bifrost needs to publish a message/event in the DOM when it is done

Implement an Execution Context for holding metadata related to the context in which a command is executed in

When a command is executed, it is being executed in a certain context. This context can contain anything. It should be a write-once object, which makes it only possible to write to when Bifrost asks for it to be populated. That way you can't populate it from anywhere and pollute it and make it a "god"-object.

Change binary output to be common drop folder

Reimplement EntityContext for TableStorage

Add build.bat / .sh files for more conveniently building the project when getting from sources

Add feature name and details onto the feature

Support multiple sources of values for service method calls

Today the existing solution for passing values along to method arguments is only using FORM values in the request. This should be refactored into something that uses a value provider model with the opportunity of having multiple providers.
For now the natural ones would be :

• Form
• Request parameters

Pack Nuget package for all projects and publish

Root of repository holds a Packages folder, within here there is a folder representing each package. Within each folder, there should be a file by convention holding information about what actual projects (By name) are involved in creating the package. For all the platforms, we will go by convention and get the binaries and put them in to the correct folder within the packages folder structure according to the Nuget convention for packages. Then the build will do a "nuget pack" based on the nuget spec.

When the revision number only changes (continuous build typically), we push the packages to our own nuget server. If the build number or any of the other numbers change (basically the revision is 0), we push to the official nuget repository.

Support multiple navigation containers with history & deepLinking on each

Today the URL that is generated when navigating says : ?feature=[name of feature], it should be more like something :
?navigation={container1:[name of feature],container2:[name of another feature]}

And also work into this parameters for the features themselves for the loaded() function that should be supported

Implement support for WindsorContainer

Cross cutting distributed caching mechanism

Design a cross cutting caching mechanism that can be used for caching entities, especially designed for EntityContext, but not tied into specifics of how caching is done for concrete implementations such as nHibernate or others.

Figure out a good design that makes it possible to have one way of enabling caching across the board for EntityContext and Views

Add support for Deactivated callback for viewModels to be called when a viewModel is going out of scope (Not on page anymore)

Cache validation rules on client for commands by its name/type

Instead of doing a post back to the server for getting validation rules every time a command is created, cache it by type name/type

behaviors, triggers and actions

Similar functionality to what is known in Silverlight for handling this

Swap out Juicer with other tool for concatenation of Bifrost JS

When the js files aren't in ANSI format, the resulting concatenated file get's some strange encoding marks.

This works fine with production code, but plays havoc when testing with jstestdriver / forseti.

Could be the runner, or could be the testing-framework (jasminebdd), but it certainly makes for some strange issues :)

Ability to specify view for features, so that a feature can have one viewModel and multiple views

Remove trailing slashes for features when loading view / viewModel

Appears to be an extra slash in the URLs generated when requiring the view and the viewModel

GET http://localhost:2787/admin/services//view.html 400 (Bad Request) text.js:7
GET http://localhost:2787/admin/services//viewModel.js 400 (Bad Request)

Create MVVM documentation

When navigating in JavaScript frontend - order of applying binding contexts are wrong

Lets say you have a main page that handles all navigation, within it it binds a to a property for feature using the feature bindingHandler.

Within the features it navigates to, there are compositions that include other features, these will get initialized in the correct order when hitting the first time, but any subsequent navigation within memory will not guarantee the ordering of initialization for the binding contexts (ViewModels)

Make the committing of a UnitOfWork / CommandContext async

When a command has gone through an event source and is ready to be committed, the client should be blissfully unaware of what happens next and we can return to the client from this point. By then making the commit async, we can return directly and just keep on processing on the server.

Add the actual feature to the viewModel prototype

Upgrade to latest knockout

Knockout 2.1.0 was released, it would be nice to upgrade bifrost to use it.

Navigation - navigateTo() function

Abstract away the History plugin and add special purpose navigateTo() function

Build and publish documentation

Build the DocumentX project and publish the resulting HTML to the Bifrost Pages and also the CHM file for downloading from somewhere

Resources through IHaveResources should support abstract methods with "dependencies" for formatting

Sometimes you have strings that need formatting - they have things that need to be dynamically replaces. In order to make these "dependencies" explicit, we should have the support for methods that should be abstract and then have the signature return a string, and the arguments for the formatting explicitly sit on the method signature

Serverside validation errors - put them back into the client

Any server side validation errors as a result of a Command execute() should be put back into the parameters validators of the command as a result

RegEx validator - implement

• ClientSide implementation
• MetaData translator

Make it possible to easily configure storage for all the different parts of Bifrost

Events, EventSubscriptions, Sagas and so forth should be able to be configured to persist to different storages. In addition, entities of different types should also be able to come from different storages.

visualStateManager - handling of visual states

Similar to what is in Silverlight, a manager for handling visual states :

<div data-visualstatemanager="[configuration]">
    <div data-visualstate="[name of state]">
    </div>
    <div data-visualstate="[name of state]">
    </div>
</div>

Configuration will contain information about all the states and configuration related to them, such as transitions between states. Animations and such.

Fix EventSubscriber logic to use the the sequential EventId that will be fixed in Issue #12

Assembly version number

Assembly version number needs to be updated during continuous integration build.

Possible strategy for versioning : http://semver.org/