![]() ![]() These Aren’t the Platforms You’re Looking for The disagreement begins when we start discussing the coupling between the concepts, particularly in relation to a platform-as-a-service (PaaS). When I talk about this model with friends and clients, I generally get some form of agreement on the concepts and structure. Every developer has a workflow (even if this is implicit), from the one-person indie website builder, to the thousand-strong team working on complex enterprise systems. Workflow: This layer is the summation of how you design, build, test, deploy, operate and observe your applications.It is also worth mentioning that I believe that you always deploy your application onto some form of platform, even if you don’t consciously assemble one. Note I’m also avoiding using the term PaaS here, which I cover later. Platform: This layer provides a coarse-grained system-level building block that may be run-time specific - such as an instance of compute with an integrated JVM or CLR - and also datastores, middleware, IAM, auditing etc.I’m avoiding using the term “physical” here, because although everything ultimately runs on hardware we are increasingly seeing the abstraction of infrastructure shift to Software-Defined-Everything (SDx). Infrastructure: This layer is the abstraction that provides raw compute resources like bare metal, VMs, OS, network, storage etc, which will ultimately be responsible for processing code and data associated with your application. ![]() Starting with first principles, I’m fairly confident in saying that all modern web-based software development involves working with three layers: He also contributes to several open source projects, writes for InfoQ, O’Reilly, and Voxxed, and regularly presents at international conferences such as OSCON, QCon and JavaOne. Daniel’s technical expertise focuses on DevOps tooling, cloud/container platforms, and microservice implementations. Daniel Bryant works as an Independent Technical Consultant, and currently specializes in enabling continuous delivery within organizations through the identification of value streams, creation of build pipelines, and implementation of effective testing strategies. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |