Notation – Bridging infrastructure and runtime code
Hey everyone, Daniel here. I’m building an open source framework that makes it easy to code and deploy serverless applications – https://github.com/notation-dev/notation | https://notation.dev. I wanted a tool that delivers the benefits of serverless (scalable managed services), but with a first-class developer experience. Here are the main concepts: 1/ Notation provides a set of primary infrastructure resources (eg API gateway, lambda, event bridge etc) that can be composed together into serverless apps. They are fully typed, so slot into place very…
What it does
In the maker’s words, at launch
Hey everyone, Daniel here. I’m building an open source framework that makes it easy to code and deploy serverless applications – https://github.com/notation-dev/notation | https://notation.dev. I wanted a tool that delivers the benefits of serverless (scalable managed services), but with a first-class developer experience. Here are the main concepts: 1/ Notation provides a set of primary infrastructure resources (eg API gateway, lambda, event bridge etc) that can be composed together into serverless apps. They are fully typed, so slot into place very easily. A lot of annoying cloud implementation details – things like constructing valid ARN strings, and writing JSON policy documents - are handled by the framework. 2/ Secondary infrastructure resources (eg IAM roles, permissions and integrations) are inferred from the relationships between the primary resources, and from explicit user intents. You can see these visualised in a generated graph. 3/ Runtime code (ie the lambda function code) belongs in separate modules – but, these can be imported into and referenced by infrastructure modules. Again, we have end-to-end types, so if a lambda function were configured to accept and API request, but got attached to an SQS stream, the compiler would quickly complain about that. 4/ Notation apps can be deployed directly to your own cloud accounts. If you want to develop locally, you can deploy using watch mode, which hot-swaps infrastructure resources, and provides snappy updates of serverless functions, while you code. The next step is to integrate more AWS services, and then later expand to other cloud platforms (feature requests ofc welcome). You can give Notation a spin at https://github.com/notation-dev/notation. I’d love to hear your feedback on the approach!
Does the same job
all alternatives →
- SCServerless Code Editor framework for any programming language2017 · github.com · ▲57
- AOAn open-source tool to deploy cloud-agnostic infrastructure anywhere2022 · ▲5
Me and a few friends have been working multy.dev, an open-source cloud agnostic API that makes it easy to deploy the same infrastructure to any cloud provider using native managed services. The motivation was the realisation that, even when using Terraform, migrating infrastructure code requires an end-to-end re-write. Even though most core resources are the same in any major cloud, developers need to learn a new provider to deploy the same infrastructure when moving providers. We currently support: - Networking (virtual_network, subnet, route_table, security_group, network_interface,…
More dev tools this month
the category →
Open-source GTM skills for technical founders
Dev tools · 29d ago · gtmcofounder.com
OpenTrailPaper is open-source bike computer firmware for the LilyGO T5S3 4.7" E-Paper PRO. It supports offline maps, GPX routes, FIT recording and Bluetooth sensors.
Dev tools · 1d ago · opentrailpaper.com
Launched alongside, January 2024
the whole month →
- IM
Life & fun · 2024 · sitinshade.com
