Show HN: attainable – The fastest and easiest way to design and deploy APIs(attainable.dev)
8 pointsby clintjhill9 days ago2 comments
  • japborst8 days ago
    Cool!

    I wonder if this isn't toooo much magic. How does this scale beyond simple use-cases? I fear one might hit a wall at 80%, where the first part is super easy indeed but not customizable enough to get to 100% of all use-cases.

    • clintjhill8 days ago
      Thanks! It's a great point to make. Early on I worked on a "migration" ability for the resources, so that every change you make automatically updates the underlying database. But the longer I worked on that, the more I realized I could create/delete as many APIs as I wanted working out what's necessary. Then scale it up for longevity. And the time it took to create/delete APIs was nearly as fast as some of the build times I've experienced for front-end applications.

      That's ultimately what I think the value is: API development as hyper-iterative as front-end apps.

      I'm still clearly working out how to describe this value. I'm developing more examples to help define what I think the best use-cases are.

  • brightbed8 days ago
    What’s the difference between the pricing sizes (micro, small, etc)?
    • clintjhill8 days ago
      Basically those plans represent the size of the clusters that are deployed for your APIs.

      All of them come with a minimum 3 node database layer, and each plan increases the node counts. The medium and large plans also increase the CPU/mem of the database nodes.