business bills Business integration Cloud containers cost effectiveness desktop environment distro-upgrade dotnet economics lamp LAN speed logistics marketing mobile phonne product life cycle profit margin psr purchasing power RPG Shipping delivery standardization Steam Gentoo gaming Transitioned economics

Heroku Symfony optionless deployment strategy

Google containers and are replacing Heroku Synfony PHP app deployment, with deployBot championing pioneer case study.

The famous Heroku soltuion, empowering deployment to gates such as PHP, Node.js, Kafka, Redis and others (ELK included), is obviously a shiny object, scam in terms of standard full fledge Symfony application deployment. It doesn’t collide with –dev and –no-dev options being installed as required.

The key hastag is, that composer Symfony project, created and developed, CI deployed, is unable being deployed because of Heroku missing strategies. Running on local symfony:local:server it conflicts with deployment agency (Heroku) it issuing statements of composer recipes warnings.

Be it minor issue, nevertheless the advertised, running and seemingly integrated API Heroku is missing its potential fulfillment – the capacity of one of the solutions in the PHP deployment agencies market is not meeting its expectations. What I recommend instead of that is and Google containers. They normally perform tasks assigned and don’t require AWS supernatural firewall knowledge. However, EC2 is nominally viable, rendering it equity transitioned, if willing (not afraid) to enounter and be open to risk and its management – timely not supervised server will cost hundreds of EUR, tens of times more than presumed, planned and expected.

%d bloggers like this: