this post was submitted on 24 Sep 2024
16 points (100.0% liked)

Web Development

3437 readers
1 users here now

Welcome to the web development community! This is a place to post, discuss, get help about, etc. anything related to web development

What is web development?

Web development is the process of creating websites or web applications

Rules/Guidelines

Related Communities

Wormhole

Some webdev blogsNot sure what to post in here? Want some web development related things to read?

Heres a couple blogs that have web development related content

CreditsIcon base by Delapouite under CC BY 3.0 with modifications to add a gradient

founded 1 year ago
MODERATORS
 

I am currently working on a fairly old website service for the company's internal needs. The stack is quite old - PHP 5.3. It so happened that company can't abandon it right now.

... In short, I received a task to develop a REST API for this service. It is clear that I cannot use the current stack. What can I use as a standalone core for the new API? The main thing for me is the speed of development and ease of learning. For example, I would like Bearer authorization / some rights model out of box.

Something like Laravel, but separate instance of it just for the API seems a little overkill for me. What you can advise me? Any boilerplates / software recommendations are welcomed.

PS: My database is MSSQL 2016, so it could be a problem.

you are viewing a single comment's thread
view the rest of the comments
[–] etchinghillside@reddthat.com 2 points 1 month ago (1 children)

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?

[–] Drun@lemmy.world 1 points 1 month ago

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.