Timeline for What is a "database"?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 6, 2017 at 0:40 | comment | added | Michael Green | So IMS DB is a DBMS but Cassandra isn't. Sorry, but respectfully disagree. | |
| Jun 6, 2012 at 20:24 | vote | accept | woliveirajr | ||
| Jun 4, 2012 at 11:54 | vote | accept | woliveirajr | ||
| Jun 6, 2012 at 20:24 | |||||
| Jun 2, 2012 at 19:20 | comment | added | Todd Everett | Thanks Aaron. My lack of experience with applications outside the traditional business application shows. I have seen a few posts, Brent Ozar for example, about data caching solutions but have never seen one in use. Thanks for your example on your previous experience. I will definitely add this concept of layering above the DBMS to enable scale out without losing the benefits of the DBMS to the toolbox! | |
| Jun 2, 2012 at 17:04 | comment | added | Aaron Bertrand | Good post. On the Craig's list thing, I think there are more layers you should consider. Storage and retrieval do not have to occur directly above the DBMS. You could certainly scale out data that is stored in, say, SQL Server without making SQL Server directly responsible for responding to user requests. There are all kinds of middle tier and data caching solutions that can aid a DBMS without needing to replace the DBMS. In my immediately previous job I used dozens of Express instances on the web servers to reduce load on the primary SQL Server - frequent pushes rather than pulls worked. | |
| Jun 2, 2012 at 16:11 | history | answered | Todd Everett | CC BY-SA 3.0 |