Casper Rasmussen Casperhr

Scaling plan for Riide Backend

last updated 16 feb 2018

MySQL is growing rapidly, 52gb (feb 2018, grows 2-3gb a week atm). This is not a urgent issue. But we need to handle this before it grows above 600GB. And the earlier we solve this. The faster is it (since you are migrating less data)
- It is possible to just buy a bigger server, but restoring backups / horizontal scaling will take days in the end
MySQL is just one RDS server. Which handles all traffic. Horizontal scaling should be looked into
Queues, jobs are too big or takes too long time.

	### Prompt: Parse pricing documents → Monta price-group XLSX (complete standalone spec)

	CRITICAL REQUIREMENT: The output MUST have EXACTLY these 14 columns in this EXACT order:

	1. Tariff
	2. Tariff ID
	3. min. Power
	4. max. Power
	5. Power Type
	6. CountryCode

	### Prompt: Parse pricing documents → Monta price-group XLSX (complete standalone spec)

	CRITICAL REQUIREMENT: The output MUST have EXACTLY these 14 columns in this EXACT order:

	1. Tariff
	2. Tariff ID
	3. min. Power
	4. max. Power
	5. Power Type
	6. CountryCode

	### Prompt: Parse pricing documents → Monta price-group XLSX (complete standalone spec)

	CRITICAL REQUIREMENT: The output MUST have EXACTLY these 14 columns in this EXACT order:

	1. Tariff
	2. Tariff ID
	3. min. Power
	4. max. Power
	5. Power Type
	6. CountryCode

	This is the exercise I propose we go through. Each line marked with a * or - needs to be a separate commit.

	Greeter
	===
	* Create an empty public repo
	* Create a readme with #World Greeter
	* Create a .gitignore

	* Tag a release 0.1

	2025-01-31 05:15:18
	2025-01-31 05:15:18 The configuration contains values or keys which are invalid:
	2025-01-31 05:15:18 selfservice: map[allowed_return_urls:[http://127.0.0.1:4455] default_browser_return_url:http://127.0.0.1:4455/portal flows:map[error:map[ui_url:http://127.0.0.1:4455/identity/error] login:map[after:map[code:map[hooks:[map[config:map[auth:map[config:map[in:header name:Authorization value:Bearer 5E3E3BA2-BFE1-48E8-B11C-65CC3711951F] type:api_key] body:base64://ZnVuY3Rpb24oY3R4KQogICAgICAgICAgICAgICAgaWYgImVtYWlsIiBpbiBjdHguaWRlbnRpdHkudHJhaXRzIHRoZW4KICAgICAgICAgICAgICAgICAgewogICAgICAgICAgICAgICAgICAgIG1ldGhvZDogInBhc3N3b3JkIiwKICAgICAgICAgICAgICAgICAgICBlbWFpbDogY3R4LmlkZW50aXR5LnRyYWl0cy5lbWFpbCwKICAgICAgICAgICAgICAgICAgfQogICAgICAgICAgICAgICAgZWxzZQogICAgICAgICAgICAgICAgICBlcnJvciAiY2FuY2VsIg== method:POST response:map[parse:true] url:http://identity:8080/identity/kratos-hooks/can-use-login-method] hook:web_hook]]] password:map[hooks:[map[config:map[auth:map[config:map[in:header name:Aut

	# Scaling plan for Riide Backend
	last updated 16 feb 2018

	### Scaling bottle necks

	- MySQL is growing rapidly, 52gb (feb 2018, grows 2-3gb a week atm). This is not a urgent issue. But we need to handle this before it grows above 600GB.
	And the earlier we solve this. The faster is it (since you are migrating less data)
	- It is possible to just buy a bigger server, but restoring backups / horizontal scaling will take days in the end
	- MySQL is just one RDS server. Which handles all traffic. Horizontal scaling should be looked into
	- Queues, jobs are too big or takes too long time.

	* Script will make sure a project has correct budgeted hours places in each month

	* "Correct" means is harvested up to today and forecasted from today and rest of the month + upcoming both

	* Script can only change allocation on unlocked months, that means if there have been errors back in time will NOT be corrected by the script

	* Script will only affect projects with "Auto assign hours" on (as beta)

	* Script will not affect project items which are value / external