I also like the idea of having the k/v datastore tightly integrated with the Dark editor

[pbiggar]

A user says:

My first experience with the editor was great, I was impressed at how quickly I was able to spin up a REST API — in about 5 seconds. Much faster than the traditional flow of: 1) set up infra 2) write code 3) test code 4) deploy code 5) test deployed code. With Dark, the flow is more along the lines of: 1) write code/deploy code/test deployed code, all in a single step. I also like the idea of having the k/v datastore tightly integrated with the Dark editor; this is a new developer experience, there aren't any workflows in the wild today (that I know of) that work like this. Working with a live database in the same editor where you write your business logic is nice.

I am just beginning to formulate ideas for how to use this tool to build some internal tools on the project I am working on in the education space. My team deals a lot with AWS and we need some tools to be able to, for example, glean information about all of our microservices, i.e., what version of each app is deployed in each of our environments in AWS. I am viewing Dark as a great way to very quickly spin up useful tools and APIs, especially from the perspective that Dark gives you a database built into your editor — this is a big deal.