My client is looking for an events implementation which could have 100's and maybe even 1,000's of events - which will be displayed on a monthly calendar. Being that I need things like documents and other entities attached to events, I was thinking of building this all out via Umbraco Doc Types. But at what point are we better off creating our own DB tables and implementations for items versus utilizing what we can do within umbraco? I see the docs talks about creating your own DB - and their example is for Blog Comments - that are not going to be Edited often if not much. Or, maybe there's something floating around in the community that already solves part of this that I'm not aware of? Most posts I've seen are from early 2010's or stopped since v8. I'm still learning on how to do things the Umbraco way 😉 Thanks

I’ll point you to one of the lesser known pages of the Umbraco documentation, specifically the “Using Umbraco content items for volatile data” section: https://docs.umbraco.com/umbraco-cms/reference/common-pitfalls#using-umbraco-content-items-for-volatile-data Generally speaking if the database is going to be hit a lot I’d advise against it. A lot of people will put events as content nodes in Umbraco, if they’re not changing a lot you will probably be okay

thanks @rickbutterfield - good to see that page again. As long as our querying is clean and concise I'm thinking we'll be ok. Again - not much experience so we haven't really scraped our elbows on anything yet.