HN user

jesses

90 karma
Posts9
Comments42
View on HN

Founder of gigalixir here. You're right, but I just wanted to mention that those limitations are for the free tier. Once you upgrade to the standard tier, both those limitations go away.

Founder of gigalixir here. We use GCP under the covers by default, but you can also choose to use AWS if you like. You can also choose which region you want to run in, but we only support us-east1 and us-west2, and on GCP: us-central1 and europe-west1.

I'm the founder of gigalixir.com, and I haven't dug into this very deeply yet, but I'll just say that from my perspective, this is great regardless of if it competes or complements gigalixir.com. Anything that helps grow the Elixir community and helps drive adoption of Elixir will benefit everyone in this space.

For databases, you can provision one through Gigalixir, or you can provision one yourself with Google Cloud SQL in the us-central1 region.

For other apps, anything running in GCP us-central1 will be in the same high latency network, but some customers interop with AWS or Heroku just fine albeit with slightly higher latencies.

Right now, the servers are on Google Cloud Platform in the us-central1 region. It's in multiple availability zones for reliability.

I highly doubt the service will be discontinued ever since traction looks good and we have plenty of funding, but Gigalixir and Heroku are almost interchangeable. The only difference really is that Gigalixir doesn't require a Procfile. However, if you fallback to Heroku, you'll lose clustering, hot upgrades, etc.

Deployment is by far the biggest pain point I've seen in new Elixir developers. Developers use Mix in development, but then build releases using Distillery for production. There are a few gotchas and pitfalls that almost everyone falls into when using Distillery like using `System.get_env` and forgetting `server: true` in their `prod.exs`. Hot upgrades can also be a source of a lot of confusion. Configuring distributed clustering in production can be tricky especially if you're running on Docker/Kubernetes/etc.

That said, I built https://gigalixir.com to try and help with some of these issues and improve the deployment story for Elixir.