So you’ve created a really neat console app, but it’s growing and you need a way to keep it all neatly organized and preferrably with some Good Practices.
The guys at Entity Framework have thought about this and structured their console app really neatly. Today, we’ll take the ninja app we built previously and make it all look pretty and stuff.
FoundationDB began with ambitious goals for both high performance per node and scalability. We knew that to achieve these goals we would face serious engineering challenges while developing the FoundationDB core. We'd need to implement efficient asynchronous communicating processes of the sort supported by Erlang or the Async library in .NET, but we'd also need the raw speed and I/O efficiency of C++. Finally, we'd need to perform extensive simulation to engineer for reliability and fault tolerance on large clusters.
To meet these challenges, we developed several new tools, the first of which is Flow, a new programming language that brings actor-based concurrency to C++11. To add this capability
| image: ruby2.0.0 | |
| script: | |
| - cp config/database.example.yml config/database.yml | |
| - bundle install | |
| - psql -c 'create extension hstore;' -U postgres -h 127.0.0.1 | |
| - psql -c 'create role exmu with superuser login;' -U postgres -h 127.0.0.1 | |
| - psql -c 'create database exmu_test;' -U postgres -h 127.0.0.1 | |
| - bundle exec rake db:test:prepare | |
| - bundle exec rspec spec | |
| services: |