meta data for this page
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| ixc2024:impactassessment:technical [2024/05/24 11:37] – joof | ixc2024:impactassessment:technical [2024/05/24 11:46] (current) – joof | ||
|---|---|---|---|
| Line 19: | Line 19: | ||
| - **Resilience** - Your system should design your system to remain operational in case of failures | - **Resilience** - Your system should design your system to remain operational in case of failures | ||
| - Error Handling: You should use exception handling in error prone operations so as to minimize crashes. Most common ones are database and network operations. | - Error Handling: You should use exception handling in error prone operations so as to minimize crashes. Most common ones are database and network operations. | ||
| - | | + | - Code: Having your code in a repository like GIT also serves as backup. |
| - | - Data: Most database tools come with backup functionalities. Try to use them as much as possible to backup your data. Cloud Databases also offer it as a service. | + | - Recovery: Create a plan on how to quickly restore your system in the event that there is a total crash. |
| - | | + | |
| - | - Recovery: Create a plan on how to quickly restore your system in the event that there is a total crash. | + | |
| + | - **Interoperability** - | ||
| + | |||
| + | - API Design: Create well-documented APIs to facilitate communication between frontend and backend. You can use tools like Postman to test your APIs and swagger for API documentation. | ||
| + | - Standard Protocols: Use standard communication protocols and data formats (e.g., JSON, XML) to ensure compatibility with web, mobile and backend. | ||