# 08-17 Trilateration Architecture Considerations

Now that I added the Python Statsworker for statistical analysis, there now needs to be a clear distinction between the functionality of the API and math part. The goal is to reduce overlap and define roles.

# Problem

Since I initially hoped that I could do everything in PHP even though it is not optimal for complex math, I already implemented some functionality in the REST API. The question that needs answering is what the plan is going to be for splitting the workload.

# Solution

From now on the REST API is solely for storing and retrieving RSSI and the regression coefficients, otherwise there is not a whole lot of logic implemented there. Python will be responsible for rssi to distance conversion, RSSI filtering and optimization. I will move everything from PHP to Python (distance conversion) so that Python can do the heavy lifting.

# Further actions

Here is the planned architecture for trilateration:

{ width=60% }