Skip to content
This repository has been archived by the owner on Jan 19, 2018. It is now read-only.

compare to dawn/dawn #15

Closed
razum2um opened this issue Jun 9, 2014 · 8 comments
Closed

compare to dawn/dawn #15

razum2um opened this issue Jun 9, 2014 · 8 comments

Comments

@razum2um
Copy link

razum2um commented Jun 9, 2014

Please could you take a look on https://github.com/dawn/dawn and say, what are the differences, pros and cons of each implementation?

@tombh
Copy link
Owner

tombh commented Jun 9, 2014

I only just saw this last night via reddit so haven't had much of a chance to look into it. I think the basic difference, as @archseer mentioned on Hacker News, is that Peas is more lightweight and less mature. Though I notice that Dawn doesn't seem to have any tests yet.

My primary goal for Peas is that it's accessible for ease of hacking - it's the People's Paas (where the name comes from). So I want the code to be obvious and well documented. I want there to be as few parts to it as possible, so no Chef, just one datastore (ie MongoDB), little to no BASH scripting, etc. The choice of a NoSQL means no DB migrations, again, for ease of hacking. I want its development environment to be as equally important, if not more important, than its production environment.

I want Peas to be a good starting place. It will probably never be the first choice for a large scale, mission-critical enterprise project. But if you're just getting into PaaS and want to understand how they actually work under the hood then I hope Peas will be the best choice.

@archseer
Copy link

archseer commented Jun 9, 2014

@razum2um I've written about it at https://news.ycombinator.com/item?id=7860047

@tombh Pretty much spot on. Our components currently take quite a while to build, but we're trying to move them onto docker/coreos, which should make deploying it and hacking around simpler as well. And yes I do agree, we lack tests at the moment, mainly because when we started, the code was not easily testable.

That said, I do hope we can find some way to collaborate between the two Ruby based PaaS-es in the future :)

@tombh
Copy link
Owner

tombh commented Jun 9, 2014

Of course, I'll be watching your project closely and seeing where I can help and learn.

@archseer
Copy link

archseer commented Jun 9, 2014

Looking forward to it! Do ping me on freenode (username there is Speed), if you have the time.

@jipiboily
Copy link

Did the state of any of the project change radically or the comparison is pretty much the same still?

@archseer
Copy link

archseer commented Aug 6, 2014

Work on Dawn has slowed down unto a gradual halt, as we have started to actively contribute to Flynn -- we shared similar goals, and Flynn is much more ambitious (i.e. deploy any app, not just web apps) as well as the architecture was better thought out, so it just made more sense to us to move our efforts there.

@jipiboily
Copy link

Awesome, thanks for the answer. Scope is indeed different and more enterprise/real life-ish for production.

@tombh
Copy link
Owner

tombh commented Aug 6, 2014

Yeah, Peas is still heading in the same direction as I've described. Basically, I'd place it somewhere between Dokku and Deis.

@tombh tombh closed this as completed Aug 6, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants