[HN Gopher] Apollo - An Extensible Docker-Based Platform as a Se...
___________________________________________________________________
Apollo - An Extensible Docker-Based Platform as a Service (PaaS)
Author : kchhina
Score : 36 points
Date : 2020-09-29 20:30 UTC (2 hours ago)
(HTM) web link (gitlab.com)
(TXT) w3m dump (gitlab.com)
| ngcc_hk wrote:
| can similar run in digital ocean? Or is Docker image be published
| in a DO droplet and update or overwrite remotely to minimise
| hacking risk.
| alpb wrote:
| Despite the nice packaging, it appears to be a single-person
| maintained project. There are quite a few reasons why no
| opinionated PaaS built on Docker Swarm or Kubernetes (maybe
| surprisingly) came even close to being a popular choice in the
| market. Usually, anyone serious who's going to bet on a PaaS that
| runs their stack will also need a serious corporate entity (i.e.
| software vendor) supporting the tools in case things go wrong.
| Similarly, often many serious companies are better own building
| their own PaaS on top of these platforms as they realize sooner
| or later, they want a lot of customization and control over the
| platform. So far I'm adding this to the pile of people who've
| tried to build a PaaS on top of docker/k8s. I'm not seeing a lot
| of features to make it stand out, what I'm seeing in the features
| section is more of an opinionated stack.
| zyang wrote:
| I remember first time seeing Elastic Search around 2012. Shay
| Banon was the sole commiter for over two years at the time.
| Never underestimate determined founders.
| gavinray wrote:
| The fact that it works with an existing docker-compose.yaml and
| will provision itself on a cloud for you is pretty compelling I
| think.
|
| I have tried the Docker AWS ECS plugin for deploying your
| compose stack, and it's buggy.
|
| The AWS ECS CLI would deploy docker-compose files in V1. V2
| (now called Copilot) has shifted away from this, and it uses a
| custom manifest YAML file. Copilot isn't bad.
|
| Most of the platforms I work on have a docker-compose stack
| with Postgres, a backend API, a frontend, and potentially
| ancillary services. Anything that integrates well with this is
| a godsend tbh, because otherwise you need to maintain two sets
| of configuration and keep them in sync.
| slayerjain wrote:
| What are other docker/k8s based PaaS you've tried?
| giovannibonetti wrote:
| What about Google App Engine Flex, Google Cloud Run and Amazon
| Fargate?
|
| In my company we have been using App Engine Flex in production
| successfully for a few years already.
| intellix wrote:
| Name is a little similar to https://www.apollographql.com/
| verisimilidude wrote:
| Also: https://github.com/ApolloAuto/apollo
|
| It's a contested open source project name, for sure.
| agloeregrets wrote:
| And let's not forget the well-liked iOS Reddit client as
| well.
|
| Or the Greek god
|
| Or the moon missions.
|
| Or Counter Culture's Light Roast beans.
|
| Basically the name is a bit tired and few actually have a
| reason to call it that. (Apollo the Reddit client to browse
| the world of Reddit which has an alien as it's avatar almost
| makes sense.)
| andrewxdiamond wrote:
| Amazon engineers will also recognize Apollo as something
| else
|
| https://www.allthingsdistributed.com/2014/11/apollo-
| amazon-d...
| randtrain34 wrote:
| This seems very similar in concept to https://caprover.com/
| whalesalad wrote:
| I've been wanting to build something like this for a long time,
| very neat. I haven't had a chance to use it yet but looking
| through the readme this is a very comprehensive project.
| gavinray wrote:
| This looks incredible! Has some serious offerings against the
| current Self-Hosted PaaS scene, hope I can check it out over the
| weekend.
|
| I have used Dokku[0] in production, and played with CapRover[1]
| on hobby projects. Flynn was like a better Dokku, before
| development died.[2]
|
| CapRover is a great experience, and it's not a toy IMO. It nails
| the role of "I want to press a button and have a self-hosted
| Heroku, with a nice dashboard, auto-provisioned HTTPS domains,
| and be able to deploy a bunch of Docker images or Buildpack
| apps." A single-node $10 box can run a good number of services.
|
| This looks well-positioned and closer to something like Nomad,
| but going through the readme I had a few questions:
| "Apollo requires a manager- or control-node. We call this
| manager-0. This node runs the entire controlplane and monitoring
| stack for a cluster and should be sized appropriately (8GB
| Memory, 2-4 vCPUs)."
|
| Is there a way to run this single-node and disable some of the
| peripherals for cheap/play $5-10 instances (disregarding best-
| practices)? An 8GB mem + 4vCPU DO droplet is $40/mo. Not an arm
| and a leg, but if you have to add at least a secondary server,
| seems like minimum would be ~$50/mo? "Your space
| has been created. Now let's cd to its directory: cd
| $HOME/.apollo/.spaces/demo-1.space"
|
| Are the Apollo Spaces not meant to be checked in to version
| control and used for infra + shared between people on your team?
|
| And final question (sorry if this is dumb):
| Automated infrastructure (currently only DigitalOcean and HETZNER
| Cloud supported)
|
| Does this mean I can still deploy to AWS/GCP, I just need to do
| it manually, or are these infrastructure templates required?
|
| [0] https://github.com/dokku/dokku
|
| [1] https://github.com/caprover/caprover
|
| [2] https://github.com/flynn/flynn
___________________________________________________________________
(page generated 2020-09-29 23:00 UTC)