Roll Your Own Platform as a Service with Docker*
What Are a Platform’s Components?
* Builders/Packagers that create a deployable artifact
* Artifact repositories to hold the deployable artifact
* Provisioners that spin-up new services
* Hosts that run a deployable artifact
* Routers/Load balancers to
* Direct traffic from the public to their nearest/most available application servers
* Load-balancers/reverse-proxies/service discovery to
* Route traffic from an application server to composing services
* Slowly ramp-up load as a new version of a service is deployed
We’ve all been there. We’ve had this lovely, monolithic application purring happily away on some platform-as-a-service. However, the application and team are growing and we need to separate out functionality into independent services to keep moving forward without stepping on one anothers’ toes.
This talk deconstructs the “perceived simplicity” of platform-as-a-services and answers some critical questions:
- What are the essential components of a Platform as a Service?
- When is building our own PaaS worthwhile?
- How and where should we leverage docker in the provision/build/release/deploy/un-provision application life-cycle?
This talk stems from a 6 month engagement building a platform as a service for a micro-service based architecture.
devops, packer, ansible, Docker
I'll be giving this talk at a variety of locations this year, including AgileIndia, a few local meetups, and potentially a few language-specific conferences.
Zee is the founder and principled consultant for Zinc Made, a business-value focused technology consultancy that streamlines business processes with custom software and hardware.
Over the past decade, Zee has built business-enabling software for companies ranging from Fortune 50 to 4 person startups. His background includes everything from interaction design to application development to designing and implementing secure, scalable custom cloud infrastructure.