jesse
Gigalixir: Platform-as-a-Service designed just for Elixir/Phoenix
Hi everyone,
I hesitated to post this here because I don’t want you to think I’m spamming, but I’ve been working on a Platform-as-a-Service designed just for Elixir/Phoenix and I’m looking for some beta testers and some honest feedback, and I thought this was the best place to look.
I call it Gigalixir, and it’s very much like Heroku except it uses supports hot upgrades, node clustering, and remote observer. It also does not restart instances every 24 hours or limit you to 50 concurrent connections per instance.
If you’re willing to give me honest feedback, I’ll happily throw $75 on your account. You can find more information about it at www.gigalixir.com and the quick start is at gigalixir.readthedocs.io.
To get access to the beta, I’ll need to add your email address to the whitelist. You can request access by emailing beta@gigalixir.com or filling out the beta invitation request form.
Please let me know if this post is considered inappropriate and I’ll remove it. If you know of a better place I can try and find feedback, I’d really appreciate it!
Thanks a lot!!
Most Liked
jesse
First of all, thanks to everyone who helped with the beta test earlier this year.
Gigalixir, a Platform-as-a-Service for Elixir, now has a free tier so you can try it without a credit card. We also added Postgresql-as-a-service, and is no longer invitation-only.
If you’re interested, we highly recommend following the quick start to get started.
As always, feel free to contact me directly for help. You can find me in the Slack channel as @jes.
jesse
@OvermindDL1 it is more expensive than bare metal and more expensive than an infratructure-as-a-service like AWS, but we think the amount of time it saves you is worth much more than what you pay. You just git push gigalixir and forget about
- Installing Kubernetes in high availability mode with multiple masters in a multi-zone configuration with autoscaling.
- Configuring ingresses, services, deployments, replica sets, pods, volumes, secrets, etc.
- Writing Dockerfiles to compile your code, build assets, build a release, and run your app.
- Managing app configuration and secrets.
- Tracking releases.
- Rollbacks.
- How to cluster nodes together: ensuring containers have network access to one another, can discover each other, and reconnect when networks partition.
- How to perform hot upgrades as easily as doing a rolling restart.
- How to connect a remote observer to a production node with SSH tunnels and iptables.
- Running one-off or batch jobs like database migrations.
- TLS certificates
- Aggregating logs and tailing them.
- Administration/Maintenance
- Stability/Reliability
- Capacity/Elasticity: ensuring you always have another machine when you need it
- Security
- Websockets: they don’t always work out of the box e.g. behind a load balancer
- Usability: making all the above easy to use
It took us 6 months to put all the above together and we have a ton of experience running apps in production. At my last company, we went from Heroku to AWS to bare metal to try and save money, but the amount of effort it took to rebuild everything we took for granted at Heroku was enormous.
If you are running 100,000 machines, then it’s probably worth the developer time to migrate off PaaS, but for most smaller companies, it makes sense to outsource the devops so you can focus on building your app and providing unique value to your customers.
jesse
@OvermindDL1 my point isn’t that PaaSes are the only right way, but that for some, it makes more sense than doing things yourself. As a sort of silly example, I’d rather buy my coffee at Starbucks than try and save money by growing my own beans, roasting them, grinding them, etc. But for some, especially those with an interest in it, growing your own beans might indeed make sense.
Popular in Discussions
Other popular topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #advent-of-code
- #elixirconf-us
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #performance









