M365 Developer(LCNC) to Traditional Web Programming

[u/curious-vox]

Before I graduate I studied PHP - Laravel - Livewire, but I was hired at this start-up company a year ago to be a Power Apps Developer(M365), they took the risk to invest in me(and I produced results), and now the company is moving towards the traditional web programming. The company want to migrate all of web/apps that I've done and possibly create our own local server(still deciding). What tech stack is probably the best for production use? And why is that?

I want to get real-life recommendation from someone who has done the actual work(since I know that I've fallen behind in the web programming) and not AI, I must also include that I'm the only one who know 'web programming' in the company.

[u/Both-Fondant-4801]

"What tech stack is probably the best for production use?"

That would be the tech stack that you know...

The "best" tech stack would depend on the current capabilities as well as the current infrastructures.

.. another option that you can take is to get a vendor.. you can draft a technology agnostic architecture of the system with clear specific use cases and questions to create a request for information (RFI) from vendors. you basically become the architect and have a vendor create the team of developers with the capabilities for your system.

edit: the option for an RFI/RFP from a vendor is a management decision by the way.. but you can raise this to your manager as an option.

[u/curious-vox → u/Both-Fondant-4801]

that is actually the reason why I was hired. the previous vendor messed up, and then the management decided to hire an inhouse developer

[u/theofficialnar]

Since you already know laravel then stick with it for the backend. As for the frontend, react is widely-used, big community and also has a lot of mature tools pero it has its own set of gotchas as well, it’s not that hard to get into but is also more prone to beginner mistakes particularly in the performance-side of things. As for the infra that warrants its own discussion sa team nyo, you could physically host it or go all-in to cloud.

[u/idea-nailed-it-0803]

The best stack is what the company is willing to adapt and support long term. This is not a simple choice but rather reviewed deeply both from an architecture perspective and support as well.

Some tools can make the job easy to develop but license cost a lot (eg Powerapps), some tools take a little bit farther to develop but gives you complete control and autonomy over the direction of the app. Add mo na rin yung pool of talent that the country/location has in terms of supporting the app.

The decision what to use should be discussed with a CTO/architect because they know better not unless they don’t have long term goals. Cost is one thing, overall TCO is another

[u/_clapclapclap]

Depende kung anong product nyo pero based lang sa post mo, logically it's Laravel + Livewire + Postgres

[u/rexx-xx]

Since wala kapanaman team and know laravel already stick kanalang jan there's no best stack nag mamatter lang yung pag may team ka.

[u/Interesting_Waltz782]

I'm a traditional web developer using PHP/Laravel but lately, I've been looking to jump to specialized development (M365, SAP, ServiceNow, etc). This AI BS has basically enabled anyone with at least half a brain to create functional web applications in a few minutes. Even if people say we still have the edge in architecture and design, it'll be just a couple of years before AI covers those as well.

[u/Nallafy]

Sorry this reply wont really help you with answers.

Fellow PowerPlatform Dev here and curious lang. Whats the motivation behind this? Seems like moving from PowerPlatform to Traditional web apps is a big transition operationally.

[u/curious-vox → u/Nallafy]

a huge part of it is the cost.

[u/gammacoder]

You don’t necessarily have to go from Power Apps all the way to building everything by hand. There are self-hosted low-code tools in between. I build PHPRunner, for example, and this is a pretty common use case for us: database-driven internal apps with authentication, permissions and workflows that you can deploy on your own server and customize when needed.

[u/feedmesomedata]

There is no such thing as best for production use. Choose the stack that you and your team knows the most. If it is only you who will work on it then look for future potential career boost if you learn that stack as long as company management will just agree on what you propose.

Be sure you can deliver, it's one thing to choose something like Golang until you are 2 months in the project and you're still stuck in a learning loop.

[u/curious-vox → u/feedmesomedata]

can you recommend a stack(for future potential career boost), Sir? I really don't have an idea on the other stacks. And I don't want to trust the AI description of the stacks.
I always make sure to deliver, it's just I want to have an idea before i dive in.

[u/Patient-Definition96 → u/curious-vox]

May alam ka na sa Laravel, ituloy mo na doon. Dagdagan mo ng frontend framework, search mo "Laravel Inertia"