Timeline for One codebase - lots of hosted services (similar to a basecamp style service) - planning structure
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 21, 2014 at 21:24 | answer | added | Jonathan Eunice | timeline score: 0 | |
| Nov 9, 2012 at 20:12 | answer | added | GrandmasterB | timeline score: 3 | |
| S Nov 9, 2012 at 20:11 | history | suggested | Andrew | CC BY-SA 3.0 |
Indent options
|
| Nov 9, 2012 at 19:57 | comment | added | Luc Franken | There is no answer to this. It is called tenancy, global info: en.wikipedia.org/wiki/Multitenancy Depending on your wishes of mostly customisation you can make a choice but it's not possible to give a concrete answer. In general if you take a look at most projects you see big data solutions. So solutions with a single data model. They solve your issues by for example sharding. But, as stated, first make your business case more clear. | |
| Nov 9, 2012 at 19:49 | review | Suggested edits | |||
| S Nov 9, 2012 at 20:11 | |||||
| Nov 9, 2012 at 19:35 | review | First posts | |||
| Nov 9, 2012 at 19:50 | |||||
| Nov 9, 2012 at 19:20 | history | asked | Sk446 | CC BY-SA 3.0 |