p.m. › 80k revenue p.m. › <1% conversion rate › No monitoring › No backup › 1 CTO ( = Backend Developer) › 1 PM › 1 Frontend Developer › 1.5 Freelance Backend Developers › Kanban = ”Build as you go” › No CI › No tests But we shipped parcels and had actual revenue! Where we started 2013
architecture › Asynchronous communication via RabbitMQ › Tooling › Switch from ZF1 to Symfony2 › Replaced github with gitlab › Rolled out message queueing › Development › Unit tests › Introduction of CI Then we built the 3rd and 4th application, breaking up monolith 1
information between systems › Systems publish their information to an Exchange › Shop: orders, customers, products › Whenever an order / customer / product changes, updates are sent › Other systems can subscribe to the updates over a standard interface › Less load, easy failover!
on Spot Bare Metal Details Technology available as PaaS Drop in replacement Temporary peaks Spin up instances in the cloud via auto scaling Can be done in parallel Not critical Always on, high memory, CPU and IO required Upsides Low maintenance High scalability Costs only for a limited amount of time Combination of low costs and highly scalable High computing power for a low price Cost Low availability cost Charged per request High, but time limited, otherwise low Low costs (80% discount) 5-10% of comparable cloud costs Examples AWS S3, Google BigQuery AWS EC2 Google Container Engine Calculate ML models on AWS Spot instances or GC Preemptibles MySQL cluster Elasticsearch cluster