You build the new API routes and all in the existing stack – slap the hood, then say – “that’ll hold”.
:(
Try and get the current stack running locally or in a dev environment. Add a “hello world” route - call it and see what happens - iterate.
There are certainly times that you come into a situation that requires a new service. But it shouldn’t be your first inclination. A lot of software development is supporting legacy/other’s code.
Do the new requirements require information from the current database/codebase?
They certainly do (from database). Maybe you're right - main reason I didn't wanted to use current stack is because outdated PHP curl (TLSv1, eh), but I can probably achieve the same with “exec”.
I'll look into that.
Why is it overkill?
Like you already have PHP in your stack, why not keep it with a new version of course...
It has so much. I think it may be a problem to maintain it just for the API. Perhaps, there’s something a little bit more compact?
Welcome to the web development community! This is a place to post, discuss, get help about, etc. anything related to web development
Web development is the process of creating websites or web applications
Some webdev blogs
Not sure what to post in here? Want some web development related things to read?
Heres a couple blogs that have web development related content