AutoFlare Overview
I’ve got a project idea, which I’ve just now decided to call AutoFlare, that I’ve been rolling
around in my head, primarily as a way to learn more about three technologies:
I’ve got a lot of experience with AWS and GCP, and there are plenty of things I like about those platforms, but I’d like to branch out, and some of the blog posts I’ve seen from Cloudflare around network egress costs and things has got me curious. I’d like to learn more about their various offerings, and play around with building a mildly complex application with just what they’ve got. (This blog is hosted by Cloudflare, as a static set of assets, which I’ve really enjoyed the simplicity of.)
I’ve got some experience with Fulcro, and, of all of the web frameworks I’ve used, it seems to be the most cohesively designed, where I don’t have to spend a bunch of time choosing and tweaking routing libraries, or storage solutions, etc. I’d like to really stretch my understanding of Fulcro with an app more complex than just the Fulcro book, thus why it’s part of this experiment.
As for Automerge CRDT, I’ve wanted to explore and learn this library since I first learned about
it. I’m really motivated by the idea of building local-first apps, and this library seems like
it’s solved a really hard problem related to building a local-first app. Also, I’ve got a vague
sense that this might be useful in luring teaching JS devs about the joys of CLJS development.
This series of posts will be different forms and formats of exploring these technologies and building this small project. Posting order will be largely dependent on my whims, and what strikes me as the most interesting thing to look at in the moment.
See you in the next post!