Magento upgrades are intense, agencies charge hundreds of hours for some. I’d say back out now before you get yourself in over your head.
Doug Hatcher
Enterprise architecture and tech junkie
If you’re interested in writing something somewhat useful, take a look at Elasticsearch which has good PHP support and is used on many projects.
Generally, I think you should build docker images and perform testing and linting against those using the functionality of the pipeline of your favorite git service. You can then trigger deployments with services that leverage docker images, and you feed it the same build images you were testing for deployments. Different applications have different deployment details, but whatever the application, if you can dockerize it then you can generally roll it out with little to no downtime, and it’s usually fairly portable to other services at that point too.
Inheritance is a good way to give objects common functionality while changing key pieces to suit different purposes. For example, you can define an interface that describes how data flows through your application. Then you can write an abstract class with the database plumbing. Then maybe you’d create a posts class to represent a collection of posts, and that class is where you’d store the logic specific to posts. In this model, there is no code duplication, and you’re using interference to share code across multiple objects that largely work the same.
You really have to appreciate his integrity, likely not an easy post for him to write. Still, it seems like an official GraphQL implementation would be prefered, and you could sunset a lot of the REST functionalities while fleshing out an API more suited for headless content management and delivery. I say merge it anyways!