Luis Rodriguez-Galvan
asked on
Switching from PHP
We have a web application in PHP (LAMP) which works pretty well.
We sell this app to companies directly. It is no for general use. So every time we sell it we installed in an AWS instance and provide the IP address and credentials to the customer.
This app is designed to work with a browser.
If I would like to convert this app to another languaje, like Go, which languaje would you reccomend that?
Thanks
Luis R
We sell this app to companies directly. It is no for general use. So every time we sell it we installed in an AWS instance and provide the IP address and credentials to the customer.
This app is designed to work with a browser.
If I would like to convert this app to another languaje, like Go, which languaje would you reccomend that?
Thanks
Luis R
I agree with David Favor.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hi,
You said that the application is working pretty well...
So why do you want to convert it?
Based on that reason you may have other options ...
You may just need a responsive template so mobile device can use it or an API to communicate with third party...
If you want your client to host themself the application and you want to protect the sources code you can use https://www.ioncube.com/
You said that the application is working pretty well...
So why do you want to convert it?
Based on that reason you may have other options ...
You may just need a responsive template so mobile device can use it or an API to communicate with third party...
If you want your client to host themself the application and you want to protect the sources code you can use https://www.ioncube.com/
Tip: When porting to another language, be sure to never touch any of your existing code. Leave it running.
Setup some other host, like https://dev.foo.com for your API dev work. This way if your project turns out to be longer or more expensive than you anticipate, you can just kill it off with no effect on your existing code.
Setup some other host, like https://dev.foo.com for your API dev work. This way if your project turns out to be longer or more expensive than you anticipate, you can just kill it off with no effect on your existing code.
There could be excellent reasons to switch from PHP to a different language or framework.
One reason is going serverless, and instead of servers you will be using cloud functions/Lambda functions.
In this case, you will have to use a language supported by Lambda.
AWS Lambda natively supports Java, Go, PowerShell, Node.js, C#, Python, and Ruby code. PowerShell is unsuitable for a high level application.
AWS Lambda also provides a Runtime API which allows you to use any additional programming languages to author your functions, such as PHP, but I am not brave enough to recommend it. https://aws.amazon.com/blogs/apn/aws-lambda-custom-runtime-for-php-a-practical-example/
Ask yourself why do you consider switching from PHP to something else.
Did the php core developer leave you and you now have a bunch of new, eager, fresh out of uni programmers with GO knowledge?
Do you want to switch to a multi-tenant architecture and someone told you that PHP sucks at it?
Are you having performance problems and the consultant told you that GO outperforms PHP on performance benchmarks?
Do you think, based on demand in your region, that PHP programming is a dead end career?
Do make a switch, but from the right reasons, and be aware of the risks to your business.
One reason is going serverless, and instead of servers you will be using cloud functions/Lambda functions.
In this case, you will have to use a language supported by Lambda.
AWS Lambda natively supports Java, Go, PowerShell, Node.js, C#, Python, and Ruby code. PowerShell is unsuitable for a high level application.
AWS Lambda also provides a Runtime API which allows you to use any additional programming languages to author your functions, such as PHP, but I am not brave enough to recommend it. https://aws.amazon.com/blogs/apn/aws-lambda-custom-runtime-for-php-a-practical-example/
Ask yourself why do you consider switching from PHP to something else.
Did the php core developer leave you and you now have a bunch of new, eager, fresh out of uni programmers with GO knowledge?
Do you want to switch to a multi-tenant architecture and someone told you that PHP sucks at it?
Are you having performance problems and the consultant told you that GO outperforms PHP on performance benchmarks?
Do you think, based on demand in your region, that PHP programming is a dead end career?
Do make a switch, but from the right reasons, and be aware of the risks to your business.
Go != PHP
Switching from PHP to PERL, as an example, will be fairly simple.
Switching to Go or Ruby or NodeJS... much more challenging.
Tip: If people are paying + happy, just keep selling your current code.
Cash the checks. Sip umbrella drinks on beaches around the world...
Summary: If it works. Keep using PHP.
If you're just looking for a new hobby + have unlimited budget... all languages are equivalent...
Just pick whichever language you'd like to learn, then strap in for a long adventure.