Reposted by Lanza
"If you don’t see the use of it, I certainly won’t let you clear it away. Go away and think. Then, when you can come back and tell me that you do see the use of it, I may allow you to destroy it."
G. K. Chesterton, The Thing, 1929.
3/
G. K. Chesterton, The Thing, 1929.
3/
November 18, 2024 at 11:03 AM
"If you don’t see the use of it, I certainly won’t let you clear it away. Go away and think. Then, when you can come back and tell me that you do see the use of it, I may allow you to destroy it."
G. K. Chesterton, The Thing, 1929.
3/
G. K. Chesterton, The Thing, 1929.
3/
I see. Great, you're already handling multi-tenancy correctly.
In case you need to, here are a few considerations to dive deeper:
- Coupling, can you use your DB without your controller safely?
- Error-handling, do you do it more than once?
This is just a heads up if you need to scale your system.
In case you need to, here are a few considerations to dive deeper:
- Coupling, can you use your DB without your controller safely?
- Error-handling, do you do it more than once?
This is just a heads up if you need to scale your system.
November 14, 2024 at 5:11 AM
I see. Great, you're already handling multi-tenancy correctly.
In case you need to, here are a few considerations to dive deeper:
- Coupling, can you use your DB without your controller safely?
- Error-handling, do you do it more than once?
This is just a heads up if you need to scale your system.
In case you need to, here are a few considerations to dive deeper:
- Coupling, can you use your DB without your controller safely?
- Error-handling, do you do it more than once?
This is just a heads up if you need to scale your system.
OOP dev here. I have some experience working with multi-tenant systems.
Here's my take.
If you only need a tool to scope your queries appropriately consider wrapping your data provider to: fetch the correct tenant & apply the correct WHERE clause. Then, update your code to use your new provider.
Here's my take.
If you only need a tool to scope your queries appropriately consider wrapping your data provider to: fetch the correct tenant & apply the correct WHERE clause. Then, update your code to use your new provider.
November 13, 2024 at 7:23 PM
OOP dev here. I have some experience working with multi-tenant systems.
Here's my take.
If you only need a tool to scope your queries appropriately consider wrapping your data provider to: fetch the correct tenant & apply the correct WHERE clause. Then, update your code to use your new provider.
Here's my take.
If you only need a tool to scope your queries appropriately consider wrapping your data provider to: fetch the correct tenant & apply the correct WHERE clause. Then, update your code to use your new provider.
Can't have enough of those! I'm not Brazilian myself but I can't recommend you enough to eat a nice local feijoada and sprinkle your beans with farofa, a 10/10 combination of Brazilian cuisine
November 12, 2024 at 10:05 PM
Can't have enough of those! I'm not Brazilian myself but I can't recommend you enough to eat a nice local feijoada and sprinkle your beans with farofa, a 10/10 combination of Brazilian cuisine