From Fedora Project Wiki
(interim save, categories added) |
(interim save) |
||
| Line 1: | Line 1: | ||
== What is the problem? == | == What is the problem? == | ||
| Line 19: | Line 18: | ||
** Everything can be replicated and made redundant (clustered, etc.) | ** Everything can be replicated and made redundant (clustered, etc.) | ||
** WSGI middleware stack | ** WSGI middleware stack | ||
== Resources == | |||
* http://fedorahosted.org/moksha | |||
[[Category:FUDConF11]] | [[Category:FUDConF11]] | ||
[[Category:FUDCon BarCamp notes]] | [[Category:FUDCon BarCamp notes]] | ||
Revision as of 17:21, 10 January 2009
What is the problem?
Lots of good Fedora services that all act differently.
The MyFedora team ran in to complexity problems, writing code specific to Fedora.
What is Moksha?
Tool for making collaborative dashboards of widgets from existing social services and applications.
What does Moksha solve?
Many, many cool things. (Raw notes from quaid 16:56, 10 January 2009 (UTC))
- Data persistence
- Scalability. Extensive caching; each app deployed has its own sqlite dbase on disk, setup by Moksha automatically.
- Everything can be replicated and made redundant (clustered, etc.)
- WSGI middleware stack