Web Development

3430 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

Follow the programming.dev site rules
Keep content related to web development
If what you're posting relates to one of the related communities, crosspost it into there to help them grow
If youre posting an article older than two years put the year it was made in brackets after the title

Related Communities

Wormhole

[email protected]

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

https://frontendfoc.us/ - [RSS]
https://wesbos.com/blog
https://davidwalsh.name/ - [RSS]
https://www.nngroup.com/articles/
https://sia.codes/posts/ - [RSS]
https://www.smashingmagazine.com/ - [RSS]
https://www.bennadel.com/ - [RSS]
https://web.dev/ - [RSS]

Credits

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

founded 2 years ago

MODERATORS

[email protected]

[SOFTWARE REQUEST] Core for new API (self.webdev)

submitted 3 months ago by Drun to c/[email protected]

6 comments fedilink hide all child comments

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.

top 6 comments

sorted by: hot top controversial new old

[–] [email protected] 3 points 3 months ago (1 children)

You build the new API routes and all in the existing stack – slap the hood, then say – “that’ll hold”.

[–] Drun 1 points 3 months ago (1 children)

[–] [email protected] 2 points 3 months 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 1 points 3 months 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.

[–] [email protected] 2 points 3 months ago (1 children)

Why is it overkill?

Like you already have PHP in your stack, why not keep it with a new version of course...

[–] Drun 1 points 3 months ago

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?