App Redundancy, Recent Updates, & Quietly Released Features
Updated dashboard UI brings your app’s redundancy to the forefront. We’ve also quietly released other features & updates over the last few weeks.
There’s been a lot happening behind the scenes here at Pagoda Box over the past few weeks. Changes and upgrades have been released with no real announcements or fanfare. This post is just a quick summary of some of those changes.
New Redundancy Visibility & Functionality, Redis Updates, MongoDB Updates, PostgreSQL, PHP Updates, New Deploy Hooks
Application redundancy is incredibly important for any application requiring “high availability”. Redundant services act as a layer of protection against potential interruptions, providing hot failover in case an instance ever becomes unresponsive.
To provide better visibility into the redundant state of apps, we’ve introduced new UI elements into the dashboard. We’ve also introduced the ability to change services’ topologies on the fly.
There is now a application redundancy summary in the dashboard. This summary shows how many of your services are or are not redundant. You can see exactly which services fall into each category by clicking on the number to the right of the grouping.
Inside of each service, there’s a an redundancy indicator above the Restart, Reboot, Repair buttons.
With the added focus on and visibility into application redundancy, we’ve also introduced “topology migrations” - the ability to change a service’s topology on the fly.
Previously topologies could only be defined when a service was created. To add redundancy to a database created with the
single topology, you’d have to create a new database with the
redundant topology, then manually migrate your data. This is no longer required. Topologies can now be changed in your dashboard.
When changed, we provision new instances using the new topology and migrate all data behind the scenes.
Note: Changing a service’s topology in the Boxfile will not change the topology on deploy. The Boxfile
topology setting only applies on service create.
For more information about application redundancy, check out the App Redundancy doc.
Redis 3.0 is now available on Pagoda Box. For details about what’s new in v3.0, check out Redis’ release notes.
Note: While Redis Cluster is included in v3.0, it is not currently available on Pagoda Box.
The “redundant” topology is now available for Redis services on Pagoda Box. It’s made possible through an internal redundant Redis project we’ll soon be open-sourcing. More information to come.
MongoDB 3.0 is now available on Pagoda Box. For details about what’s new in v3.0, check out the MongoDB release notes.
The “redundant” topology is now available for MongoDB services on Pagoda Box.
The release of PostgreSQL was announced a few weeks ago, but we wanted to list it here as well. It has been a highly requested service that many have already started using.
The “redundant” topology is available for Postgres services on Pagoda Box. It’s made possible through an internal redundant Postgres project we’ll soon be open-sourcing. More information to come.
Updated New Relic Agent
The New Relic PHP Agent was updated to v22.214.171.124. For details about what’s new, view the New Relic PHP release notes.
New & Updated PHP Extensions
The following PHP extensions were added and updated:
- phalcon (upgraded to 2.0)
New Types of Deploy Hooks
Two new types of deploy hooks are now available on Pagoda Box -
after_deploy_all. These are the same as
after_deploy hooks, except that in multi-instance services, they run on all instances instead of just one. They’re really handy when using deploy hooks to modify files inside of nonpersistent writable directories, which are local to each instance.