0 cost architecture

Static pages generated with pre-rendering can be hosted on any cdn. Also do includes GitHub for organizational websites that don’t violate terms of service. Guthub has some strict and highly left winged restrictions. Any sites that are in that realm can be easily hosted else where.

The simplest Druid site is made up of panel pages that don’t use databases of any type. An experience that fits this model is a blog or portfolio website. Every physical blog post can be deployed as a physical page. Same is true for pages on a portfolio website or small business informational site. Like a static menu for a restaurant.

The above experiences can be deployed as a GitHub organizational pages site. So long as they don’t violate terms of service of GitHub. This architecture runs at no cost at all.

The next level would be sites that could violate GitHub and Ernst of service. In that case an alternate cdn will be needed using a company with less strict / left wing content censorship mentality.

Alternatives:

• aws s3 + cloudfront
• azure
• gitlab?
• others

The above area needs a bit more research about what type of content is restricted by vendors providing these services.

An important price of this is being able to retain panel pages without cloud. Therefore, a adaptor for the file system, mongodb, or way to persist idb will be necessary.

The next level uses a database. In theory any database can be used. However, Druid takes an opinionated approach to support. Options outside Druid core support will need to have adaptors created. Possibly reintegrated back into core. As a one man team I can only focus on support of technology that I believe in and isn’t outdated. However, the platform is flexible enough to create adaptors for any database.