draggha / klendathu Goto Github PK

MySQL or NoSQL?

Pick one and stick with it!

Goals

• Think of an API for the frontend (How to build the EventBus adresses to request data from the backend?)
• Think of an API for the backend (maybe this will be covered by a Verticle for that particular database)

Candidates

1. Thorax
2. Marionette
3. Knockback
4. Ember
5. Angular

Criteria for this library:

1. All possible synergies with vertx are preferred over fancy features => E.g.: Try to attach the communication over the EventBus to a router/service (Backbone.Router, Ember.Router, Angular Service) in a way that doesn't feel grafted onto the library.
2. The Handlebars templating enginge is a good candidate, because vertx already supports it on the server side. But don't deem all other libraries unworthy to look into just because of that!
3. The documentation's quality (and quantity) => Which one covers more complicated templating topics? Which one has templating concepts that are easy enough to understand so you don't need the docs as much?
4. Tutorials and or docs on more complicated templating logic => It can never be future proof, but take as much as you can with your templating engine of choice. Prefer pluggable libraries over non-pluggable ones.
5. Identify what the library can and can't do (don't hop on the EmberJs/AngularJs bandwagon if you don't need most of their goodies)

Goals

• Create/edit/delete test cases for projects
• A test case is a superset of tests or cards (as in trello) => it holds all information for your tests
• A test case can contain other test cases and tests/cards
• Add information to test cases and make them dependent on their parent as well as their children => if a test fails the whole tests case has to raise an alarm. This alarm is being thrown upwards the dependency chain until the last test case in the line.

Goals
The following things must be implemented:

• create/edit/delete projects
• add information to projects (name, uid)

Candidates

1. Self made server
2. Yoke
3. ? (search for more alternatives!)

Sanity Check:

• Flexibility vs. rich ecosystem
• Is Yoke easy to extend?
• Do I need something special?
• What does Yoke middleware cover? Are there any side effects?
• Does Yoke have a router for SockJs/EventBus "routes"? Can a middleware cover this sufficiently?

Implement Tests/Cards

Goals

• These are the most atomic elements, they contain all needed information to fullfill one test. Their result will be saved locally and reported to the parent test case.
• Needed information to store: title, UID, text, media (attachments)

Candidates

1. Webpack
2. RequireJs

I would love to work with Webpack, but it would make Node.js mandatory as a build tool. Got to think about that.

Goals

• Show dependencies between modules and/or libraries
• Only use libraries that are already loaded and known
• Don't use "one file to rule them all" in development
• If possible don't use "one file to rule them all" in production (Webpacks chunks are really tempting in this regard)

Goals
The following things must be implemented:

• create a user management with Mozilla Persona