When creating a Notion-inspired app, do you treat databases as blocks (like pages or text elements) or handle them as entirely separate entities?
hey, i kinda lean that databases should be like blocks. it makes integration with pages feel more natural, though it might nee extra tuning for perf when things scale. no one fix answer tho, so do what works best for your app
In my experience, treating databases as distinct yet integrable elements rather than strict blocks provides the best of both worlds. This approach allows databases to retain their specialized functions while still enabling a smooth, page-like integration for a cohesive user experience. Over time, I’ve found that this dual treatment simplifies internal logic and flexibly meets performance demands, even as systems scale. It might involve some initial design challenges, but the benefits of clearer data handling and extensibility typically outweigh the extra effort required in development.