Most active commenters
  • dubcanada(3)

←back to thread

DigitalOcean App Platform

(pages.news.digitalocean.com)
646 points digianarchist | 18 comments | | HN request time: 0.001s | source | bottom
1. bizzleDawg ◴[] No.24698627[source]
I'd be interested to know if this is integrated and rebranded nanobox [0]? Or something completely from scratch?

[0]: https://nanobox.io/

replies(6): >>24698656 #>>24698770 #>>24699015 #>>24699941 #>>24700837 #>>24707772 #
2. phildougherty ◴[] No.24698656[source]
We certainly took a lot of inspiration and leaned on the awesome experience of the nanobox team, but this is largely a completely different architecture.
replies(2): >>24699024 #>>24699475 #
3. 101008 ◴[] No.24698770[source]
I am out of the loop, but at a quick loo it seems nanobox provided a way to deploy apps on top of Digital Ocean. Since you said "integrated and rebranded", does that mean DO bought nanobox? Or they just "copied" it*?
replies(1): >>24698909 #
4. anuragsoni ◴[] No.24698909[source]
Nanobox was acquired by Digitalocean. More details at https://www.digitalocean.com/blog/digitalocean-acquires-nano...
5. dubcanada ◴[] No.24699015[source]
It's completely from scratch, and based on playing around with it, it's a weird kubernates system. Which is why the pricing seems super weird compared to existing DO products (100GB's base and then you pay per a GB).

Nanobox was a tool that allows you to build and manage a container with setups for heroku build packs. It handled deployment, load balancing, etc. Similar to heroku for example. But it also worked with Vultr, Amazon, etc.

6. sciurus ◴[] No.24699024[source]
Can you tell us anything about the architecture?
replies(2): >>24699163 #>>24701598 #
7. phildougherty ◴[] No.24699163{3}[source]
We will be revealing a lot more about the architecture at our upcoming virtual conference called Deploy that is happening Nov 10-11th. There are a few sessions that touch on how the platform was implemented and I encourage you to tune in for those! (schedule to be announced soon). https://www.digitalocean.com/deploy/
8. Existenceblinks ◴[] No.24699475[source]
Wasn't the Appsail nanobox? IIRC, it was planed to be DO's PaaS, so it's cancelled and then DO's PaaS is based on k8s instead?
replies(1): >>24699557 #
9. dubcanada ◴[] No.24699557{3}[source]
Appsail was nanobox from what I saw, they redid it between appsail and "apps".
replies(1): >>24699607 #
10. Existenceblinks ◴[] No.24699607{4}[source]
If Appsail was cancelled, what's the point of nanobox acquiring .. I wonder?
replies(1): >>24700418 #
11. JamiePrentice ◴[] No.24699941[source]
I was hoping to see more about what happened to Nanobox after Digital Ocean aquired them. I thought what they had was really well done and was excited to see where they took it.
replies(1): >>24700841 #
12. dubcanada ◴[] No.24700418{5}[source]
Maybe an acquihire? I don't recall seeing any of the nanobox people even mentioned or reply in any of the slack messages. So I am not really sure.
13. aitchnyu ◴[] No.24700837[source]
I was guessing KNative, which powers Google Cloud Run.

https://knative.dev/

replies(1): >>24701606 #
14. bizzleDawg ◴[] No.24700841[source]
Yeah, I've been keeping an eye on their site which seems to indicate they were going to release something. I guess that's not happening any more!
15. alexellisuk ◴[] No.24701598{3}[source]
This is what I found out by printing the environment variables: https://twitter.com/alexellisuk/status/1306343018488791040
16. alexellisuk ◴[] No.24701606[source]
Google's Cloud Run the SaaS doesn't use KNative + K8s under the hood. It just uses a compatible HTTP API.
replies(1): >>24704933 #
17. coryrc ◴[] No.24704933{3}[source]
That's correct, though "Cloud Run for Anthos" is KNative + k8s + secret sauce though (I work on it).

Google has reached Microsoft-level naming complexity...

- https://cloud.google.com/anthos/run/

18. tpetry ◴[] No.24707772[source]
It‘s so sad nanobox was acquired and now trashed by digital ocean. It was comparable to a dokku/flynn on steroids, it was a very promising stack for self-hosted herokus.