Coming to an End

As I indicated in my last blog post, I've ran out of ideas and enthusiasm for this project. It does its job - less well than Bascule, but it is functional. I feel that some of the choices I have made through this project are limiting its capacity to grow - most fundamentally, by avoiding an underlying SQL or NoSQL database, I've instead ended up with a clunky flat-file JSON database instead.

It's time to think about what the next project might be.

This isn't to say that Cantilevers has been a waste of time. I have learned a lot, I've stretched my skills, I've learned new frameworks and am much more familiar with AWS serverless computing.

I'd like to extract my AWS Lambda routing module from this project and turn it into a standalone library that can be used in the future. I am quite proud of that module, though of course there are improvements and changes to be made. I am not quite sure how I can make the module standalone, as it's pretty tightly tied to my CDK build scripts for Cantilevers. But there must be a way.

So, my next steps:

1. Create a lambda router library based on my existing work
2. Start a new project using the new library
3. Profit?

So.... what shall the router be called? I'll be back in a month once I've thought of a project name!

Update - the new project is called APIViaduct and I am moving Cantilever to use it as a library.