Shannon Williams (@smw355, President @AcornLabs) & Darren Shepherd (@ibuildthecloud. Chief Architect ) talk about abstracting away dependencies for developers and packaging in Acorns. We also cover the announcement of Acorn running in AWS.
SHOW: 765
CLOUD NEWS OF THE WEEK - http://bit.ly/cloudcast-cnotw
NEW TO CLOUD? CHECK OUT - "CLOUDCAST BASICS"
SHOW SPONSORS:
SHOW NOTES:
Topic 1 - Welcome back to the show. We’ve spoken a few times over the years. First at cloud.com, then at Rancher. For those that aren’t familiar, give everyone a quick background.
Topic 2 - This core team has been working together for over ten years and have been through 3 startups now. What makes you want to do it again?
Topic 3 - Let’s talk Acorn Labs, what is the problem you’re trying to solve in the market? Explain to everyone the concept of an application development framework.
Topic 4 - Anything new going on? Announcement of Acorn running in AWS
Topic 5 - You use terms like Acorns, Acornfiles, Acorn services, and even nested acorns. Can you explain the architecture design and how it all connects together? What all are you packaging up (Docker images, configuration files, etc.) What are the advantages to this?
Topic 6 - Can Acorn be considered a runtime abstraction layer?
Topic 7 - This is sort of like a PaaS, or PaaS-like. None of the cloud providers have a service like this on top of their Kubernetes services. What do you know that they don’t
Topic 8 - How do you balance the specificity of individual cloud service but at the same time present a common interface/layer to developers?
FEEDBACK?
FEEDBACK?