- Launchpad Entry: NovaSpec:no-db-messaging
Right now, the communication between components in Nova occurs through rpc.cast and rpc.call (which uses rabbitMQ to pass messages). In many cases we only pass the id of the object in the message, and the component on the other end looks up the object in the database. This means we are essentially using the database to pass data between components
In preparation for separating the services into separate projects, it is important that we make sure that all relevant data is passed between components in the message. This will pave the way for the different components to have separate databases.
You can have subsections that better describe specific parts of the issue.
This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:
Should cover changes required to the UI, or specific UI that is required to implement this
Code changes should include an overview of what needs to change, and in some cases even the specific details.
- data migration, if any
- redirects from old URLs to new ones, if any
- how users will be pointed to the new way of doing things, if necessary.
This need not be added or completed until the specification is nearing beta.
This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.
BoF agenda and discussion
Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.