Making changes to applications has always been difficult. DevOps and Microservices introduced new techniques to simplify that, but also introduced new challenges that can be difficult to manage. Should things be easier for Devs or Ops?
SHOW: 603
CLOUD NEWS OF THE WEEK - http://bit.ly/cloudcast-cnotw
CHECK OUT OUR NEW PODCAST - "CLOUDCAST BASICS"
SHOW SPONSORS:
- BMC Wants to Know if your business is on it's A-Game
- BMC Autonomous Digital Enterprise
- Polyscale.ai - PolyScale solves global database latency and performance with intelligent serverless caching and compute at the edge.
- Check out PolyScale’s global edge data platform at www.polyscale.ai and sign up for a free account today.
SHOW NOTES:
- Microservices: Why are we doing this? (Michael DeHaan)
- Why developer freedom might be worth microservices headaches (Matt Asay)
DEVELOPERS WANT MORE FREEDOM TO CHOOSE AND MAKE CHANGES
Since the earliest days of PaaS, developers have wanted more freedom to choose how they build applications, and wanted less to distract them. But those trade-offs move the challenges of managing applications to different areas.
HAS DEVOPS FIGURED OUT HOW TO BALANCE THOSE TRADEOFFS PROPERLY?
- PaaS platforms have challenges when the use-cases drift outside the guard-rails.
- We can give developers freedom, but that often leads to silos or snowflakes.
- We don’t need containers or immutable systems, but the alternatives can be prohibitively expensive or add security risks.
- DevOps assumes that Devs and Ops can work together, but that assumes that individuals within teams all have the same goals, motivations and timelines.
- Some technologies have emerged to fit into these new working models (e.g. Kubernetes, Service Mesh, etc.)
- “If it’s 2pm on a Wednesday, and your team wants to roll out a new set of application features into production, how confident are you that the business won’t skip a beat?”
FEEDBACK?
- Email: show at the cloudcast dot net
- Twitter: @thecloudcastnet