miniflare VS awesome-paas

Recently Cloudflare introduces Miniflare. As its name suggests, Miniflare is a feature-rich but miniature version of Cloudflare worker. Miniflare is a simulator that provides an environment for developing and testing Cloudflare worker scripts locally. Miniflare is written in typescript and supports most of the Cloudflare worker features like the KV database, durable objects, WebSockets, etc.

Another implementation of the above is Cloudfare workers you might be capable of grasp some ideas from here https://miniflare.dev

Is there an ETA on Miniflare v3? Ran into a problem recently using overlapping keys with forward slashes as they were not sanitized properly: https://github.com/cloudflare/miniflare/issues/167

The KV API is only available on Cloudflare Workers. But, during development, Rakkas runs our app on Node.js. Fortunately, the Miniflare project has a KV implementation for Node. The other two packages that we've installed (@miniflare/kv and @miniflare/storage-memory) are what we need to be able to use the KV API during development. Let's create a src/kv-mock.ts file and create a local KV store to store our ublog posts ("twits") while testing:

I used hono (a wrapper around miniflare) to handle some of the boilerplate around request and routing logic. It's also refreshingly fast! 🔥

The simple explanation is that I'm proposing use of the Service Worker API. Cloudflare offers a flat, free, 100k requests a day if you can keep it cutting edge, has local development and testing options with miniflare and a key/value (KV) store.

When we run the dev script, this will ensure that the local runtime environment Miniflare will bind a KV with the name sessionStorage to our Pages function.

Slshx is a library for building strongly-typed Discord commands (https://discord.com/developers/docs/interactions/application...) that run on Cloudflare Workers (https://workers.cloudflare.com/), using a React-inspired syntax (hooks and JSX). It supports all Discord command types/options, autocomplete and interactive message components. During development, it automatically deploys your commands whenever you change your code.

I created this because I think Cloudflare Workers are a great fit for hosting Discord commands, but there wasn't an easy way to get started that had a fun development experience. I also wanted to see what a Miniflare-first (https://github.com/cloudflare/miniflare) library could look like.

Hey there. Firstly, Congratulations on the progress. From the screenshot, I can tell you the UI/UX is great. I have been maintaining Awesome PaaS [1]. Overtime, I have started feeling this space has become commoditised. Because of containers, kubernetes etc. this has been an explosion in the number of tools in the space, however in your case, because of the django/python niche you might have something. In my opinion, very few early stage apps fit into PaaS model, most of the orgs have so much customization that it hard to fit them into your platform. I guess with Django as framework specialization this won't be a problem. Goodluck, with your endeavours.

[1] https://github.com/debarshibasak/awesome-paas

There's been a number of these projects out there. I think the biggest part developers misunderstand when building these is that your target audience either knows AWS enough to build all of this with Terraform / CDK, or they don't know enough about AWS to know which tool they need to use to get done and they use something like Elastic Beanstalk or Amplify. Unfortunately the market for something in the middle is almost non-existent.

You will literally be joining a market that's already over saturated with "Deploy your apps 100x faster/easier/better/safer/secure" platforms. Here's a running list of ones that exist: https://github.com/debarshibasak/awesome-paas

My argument is that most of the small business and startups struggle to make revenue from get go. Asking for revshare, when it is day-0/day-1 kind of situation can hit the startups, small business, individuals really hard.

To me the your model looks very close to a royalty structure. Which is bad on books if you have seen "Shark Tank". It can be a fun place to host apps for indie hackers.

Another argument is that, Major cloud providers give away a lot of credits for various services. It can go upto $100k. I would even argue that you don't need devops or specialized team from you are a small org, startup and your operations are small.

Anyways, Looks like a fun project would love to list you on my Awesome Paas[1] list.

[1] https://github.com/debarshibasak/awesome-paas