Level 122
I thought you were worried about the amount of time you had available? Why throw in a bunch of unrelated technologies?
1 like
Dec 15, 2023
4
Level 4
Appwrite or Laravel
I need further insight into this situation. I can use Laravel very well and am comfortable with in fact we use it at work. Still, I have some personal projects that I would like to do which include developing the backend with Laravel and maintaining the server, especially at scale may not be sustainable both financially and manpower being the only one that will be working on those projects.
Doing some research on solving this I found some options and Appwrite (cloud) stood out among them, since I am comfortable working with React even next js, I read through the docs of Appwrite and I can have a good grasp of its major concept.
so my thought now is, to use Appwrite to simplify the backend work while I will just use something like next js to focus on the frontend based on the available resources.
above are my contemplations, I need more insight from experts in the community.
Level 75
hands and cost of maintenance with growth.
Use the most backwards compatible technology then.
There are some where the code you write today will still work 5 years from now (maybe minor tweaks needed).
But some packages and or libraries you need a 40 to 50 percent rewrite it seems.
I like the following:
- Java now jakarta ee
- php
- laravel (none of the starter kits)
- a custom php framework I keep updated over time
- fetch js
- regular javascript
- regular css
I have been learning some node js, however I do not know what sort of backwards compatibility it has or will have.
But laravel without a new starter kit has pretty good backwards compatibility, so does php.
Php usually just needs a very few tweaks to keep it up to date. The trick is to keep up with the change logs when they come out.
Please or to participate in this conversation.