Welcome to another VSHN.timer! Every Monday, 5 links related to Kubernetes, OpenShift, CI / CD, and DevOps; all stuff coming out of our own chat system, making us think, laugh, or simply work better.
This week we’re going to talk about the current trends in software architecture for Cloud Native applications.
1. How much do the Agile and DevOps principles align with the idea of software architecture? It turns out that “following a plan” and “comprehensive documentation” are “items on the right”, which, according to the Agile Manifesto, are always valuable. Isaac Sacolick from InfoWorld explains the principles behind the Continuous Architecture Manifesto.
2. How to define software architecture? What does a System Architect actually do? How do you integrate software architecture in modern software design processes? This fantastic presentation from 2019 by Dylan Beattie provides answers to these questions, and more.
3. “Early-stage startups shouldn’t run on Kubernetes yet” says Matt Rickard, suggesting instead an architectural four-stage process for them to grow through: containers, serverless, managed Kubernetes, and finally self-hosted Kubernetes.
4. The team behind the de facto standard for corporate Git hosting, GitLab, is very happy to work on a monolithic application built with Ruby on Rails. Sid Sijbrandij, founder and CEO of GitLab, explains on The New Stack why they aren’t moving to microservices anytime soon.
5. O’Reilly has recently compiled a free collection of stand-alone chapters from several of its published and forthcoming books about Cloud Native architecture patterns into a freely downloadable volume; an absolute must-read for all architects out there.
BONUS ITEM 6. We know that ORMs are getting a bit of backlash lately, but they are certainly useful in some contexts, for example to get MVPs up and running quickly. Bun by Uptrace is a SQL-first Go ORM for PostgreSQL, MySQL, MSSQL, and SQLite.
Are you a monolith or a microservices type of person? How does your team or organization deal with architectural issues and processes? Would you like to share your own experience around Cloud Native architecture with the community? Get in touch with us, and see you next week for another edition of VSHN.timer.
PS: would you like to receive VSHN.timer every Monday in your inbox? Sign up for our weekly VSHN.timer newsletter.
PS2: do you prefer reading VSHN.timer in your favorite RSS reader? Subscribe to this feed.
PS3: check out our previous VSHN.timer editions about Architecture: #25, #34, #60, and #79.