Update README.md

README.md

@@ -122,7 +122,7 @@ Not every single piece of infrastructure needs every single item on the list but
 | &#9744;   | <details><summary>Configure backup</summary> <p> Configure backup for all of your data stores, ensuring they are geo-redundant. Most Azure-managed data stores, such as Azure SQL, support automated backups. For backing up VM instances and attached disks, consider using [Azure Backup](https://docs.microsoft.com/en-us/azure/backup/backup-overview). </p> </details> |
 | &#9744;   | <details><summary>Configure cross-subscription backup</summary> <p> Copy all of your backups to a separate Azure subscription for extra redundancy. This ensures that if a disaster happens in one Azure subscription—e.g., an attacker gets in or someone accidentally deletes all the backups—you still have a copy of your data available elsewhere. </p> </details> |
 | &#9744;   | <details><summary>Test your backups</summary> <p> If you never test your backups, they probably don't work. Create automated tests that periodically restore from your backups to check they are actually working. </p> </details> |
-| &#9744;   | <details><summary>Set up schema management</summary> <p> For data stores that use a schema, such as relational databases, define the schema in schema migration files, check those files into version control, and apply the migrations as part of the deployment process. See [Flyway](https://flywaydb.org/) and [Liquibase](https://www.liquibase.org/). </p> </details> |
+| &#9744;   | <details><summary>Set up schema management</summary> <p> For data stores that use a schema, such as relational databases, define the schema in schema migration files, check those files into version control, and apply the migrations as part of the deployment process. See [Flyway](https://flywaydb.org/), [Liquibase](https://www.liquibase.org/) and [Rumba] (https://www.dbinvent.com/). </p> </details> |
 
 ### **Scalability and High Availability**