The latest articles on DEV Community by David Griffin (@findgriffin). https://dev.to/findgriffin https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F416133%2F35b40c9b-ba3f-49d4-8a60-c35fe17dbe87.jpg https://dev.to/findgriffin en David Griffin Mon, 13 Jul 2020 16:59:18 +0000 https://dev.to/findgriffin/what-do-developers-want-oop https://dev.to/findgriffin/what-do-developers-want-oop <p>It's now been over 14 years since AWS launched the Simple Storage Service (S3), Simple Queue Service (SQS) and Elastic Compute Cloud (EC2). These three services ushered in the modern era of <em>cloud</em> as a set of utility services that developers can build on top of.</p> <p>Since then, we've seen attempts to redefine cloud in terms of <em>Platform as a Service (PaaS)</em> starting with Heroku and Google App Engine (GAE) in 2008. <em>PaaS</em> has been through several iterations, but Kubernetes is currently the most popular tool for building <em>PaaS</em>-like services. It has garnered a huge amount of developer mindshare, vendor support, open-source contributions and attention.</p> <p>We've also seen the <em>serverless</em> revolution kicked off with AWS Lambda in 2014. <em>Serverless</em> has been massively popular with a subset of developers, and also has lots of community support, educational resources, and so-on.</p> <p>But while working at AWS and as part of the EC2 team, I realized that lots of the design choices and APIs in the cloud are driven by what is feasible to build. Sure, AWS tries to "work backwards" from the customer, but many AWS APIs seem like they are <strong>working forwards</strong> from design or physical constraints. Why do Lambda functions need to mess with networking and IP addresses? Why is AWS billing so complicated? Why does AWS need 200+ services? Why is DNS so hard?</p> <p>If the current set of cloud services is not the end of the road, then what comes next? Will containers, or EC2 be like the humble array or class, and be taught to new developers for decades to come? Or, will they be like the FORTRAN programming language, mostly consigned to the dustbin of history? Or, will they be like the C programming language, used for low-level tasks, but not by the majority of developers?</p> <p>Will so-called NoCode or low-code solutions be the future? Will it be platforms like <a href="https://glitch.com/">Glitch</a> targeted at specific languages or communities?</p> <p>I'm curious what people think.</p> discuss serverless kubernetes