Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to Safari
Join our communityTop Con
•••
Top Con
•••
Top Pro
•••Top Pro
•••
While this has vastly improved with the introduction of block storage (encrypted replicated, network attached storage), "spaces" (object storage), load-balancers, etc... there is still a lot a developer would miss coming from such complete ecosystems as AWS, Azure, or GAE. It's not uncommon to set up your own backups, fail-over, load-balancers, orchestration/scaling, distributed storage, distributed database. etc. For those comfortable with orchestration this is fine, and the prices of droplets are low. However there are new users who don't seem to understand that the responsibility for orchestrating availability, backups, recovery, etc. is on the user. See More
While starting with Heroku is fast and easy, and the first few deployments are actually very fast, larger applications tend to have slower deployments. It takes some time for the dynos to restart and while they are restarting the application is completely offline. Which means that you can lose precious seconds of application time. See More
Aldryn Cloud takes django CMS a step further by facilitating modern, independent collaboration practices. It’s designed with real-time collaboration in mind and to help increase work productivity. Aldryn allows you to work with two classes of user, Collaborators and Clients (CMS-only users). See More
Within the dashboard it's very easy for any user to access projects and create/deploy new ones. But with tools like the Command-Line Client that allows local development, Aldryn users are in charge of their code and have complete access (full project source code access, full database access, full Git repository access). With Aldryn web professionals avoid to repeat the same tasks over and over again, but it's not a platform for occasional web creators. See More