...
| Drawio | ||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
The table below illustrates where there are strong links between requirements and platform planning outcomes, but it is useful to consider
| Requirement | Description | Strongly linked to |
|---|---|---|
| Security considerations | Does the solution handle sensitive data?
|
|
| Recovery (RPO, RTO) | Resilience to system and data loss - Recovery Point Objective (RPO) and Recovery Time Objective (RTO) |
|
| Phyiscal location of users | Is there a large user base, and this is geographically scattered? If so, over what regions? Are a lot of the users home works, with variable and unpredictable home internet connections? |
|
| Performance requirements |
| |
| Current infrastructure | Fit it with current standards and skills |
|
| Coroporate software licensing | Cost considerations - can we use existing licences for operating system and database? |
|
The following links cover each of the above planning outcomes.
This is part of a process to go from planning to a full installed PhixFlow, which generally follows the following path
...
System planning
...
In many cases, a proof of concept installation of PhixFlow is created early on in discussions, with only minimal consideration of long term planning concerns, and this runs through to the point at which PhixFlow is made avaiable on the fully planned platform.
The proof of concept build can be on any platform set up that meets the minimum system requirements, but we have also provided an example installation that you can run through, based on the Ubuntu distribution on linux, and the MariaDB database, from initial server creation to a fully operational PhixFlow.
...
- System planning - establish planning outcomes, indicative server sizings, proposed network topology, security frameworks, location for solution
- Detailed infrastructure planning - servers configuration, including disk partitioning, network and network components, operating system
- PhixFlow installation - PhixFlow platform components (database, Java, Tomcat) and PhixFlow itself
This is by no means . In many virtualised platforms, databases will the either hosted as cloud native (or "serverless"), or will be created using pre-created image which includes partitioning of the server disks as well as the database installation itself.
System planning
| Child pages (Children Display) |
|---|