I signed up for your service - two things I noticed. One, the github was authenticating with app called digger.dev by motatoes and not alicorn, the page I landed on. Also, it took me to app.digger.dev, felt like bait and switch. I created an app. It has been stuck in deploying state for 9 hours now[1] You can't say that I didn't give your product a fair shot. I might conclude that I have trust issues with your produc…
Show HN: Alicorn Cloud – Easily move between AWS, GCP and Azure
41–46 of 46 posts
Re: Show HN: Alicorn Cloud – Easily move between AWS, GCP and Azure
#42Did someone ran into this? I'd look into it myself, but thought I'd ask first.
Re: Show HN: Alicorn Cloud – Easily move between AWS, GCP and Azure
#43Cool concept, but I have a couple of unanswered questions. - The docs link to digger and I don't really understand what Alicorn is. Is it just a GUI for resources defined using digger? - The digger docs look unfinished, e.g https://learn.digger.dev/overview/understanding-targets is missing. - From my understanding, to achieve cloud-agnostic infrastructure specification, digger abstracts the individual pieces of the i…
We launched Alicorn to focus on one thing only: multicloud. Digger value prop was less clear. Under the hood Alicorn uses same Digger engine, but adds PaaS mode as a starting point and Kubernetes to be truly cloud agnostic.
Understanding targets docs fixed- thank you for pointing that out!
The missing bit for cloud agnostic specs is targets. It's essentially a meta-template, collection of "Terraform generators" that take in higher level stack definition aka "infrastructure interface" and producing Terraform specific to a given cloud provider. You don't have to provide it, but you can customise Targets, or built entirely bespoke - it's essentially TF + basic templating on top.
Check out https://github.com/diggerhq/target-fargate as an example
Re: Show HN: Alicorn Cloud – Easily move between AWS, GCP and Azure
#44Deploying an example backend "a-nodeapp", it fails for me with the "[Sun, 15 Aug 2021 12:58:53 GMT] unable to prepare context: path "./app/" not found" message. Did someone ran into this? I'd look into it myself, but thought I'd ask first.
Re: Show HN: Alicorn Cloud – Easily move between AWS, GCP and Azure
#45My thought when I saw the name: alicorncloud - alicloud - alibaba cloud
Re: Show HN: Alicorn Cloud – Easily move between AWS, GCP and Azure
#46Earlier quoted context omitted.
Things like Dynamo are AWS-specific, it is their way of locking you in. You could use MongoDB or Cassandra (which is right depends on what you use it for) that would work in any cloud provider. Moreover, for 90% of use cases the capabilities of good old PostgreSQL are more than sufficient, even if you store JSON in it and use it like a document DB.
Try Alternator from ScyllaDB to break that lock :)
Yes, for folks who do not know, you can use Scylla, a NoSQL database that has a DynamoDB-compatible API, to deploy to other clouds (GCP) or even on-premises. It's been running in production for some years now. Here's the blog when we announced it, and there's more to be found on ScyllaDB.com — just search for "Alternator."
https://www.scylladb.com/2019/09/11/scylla-alternator-the-op...