(Admittedly, @nicolefv, @jezhumble and @realgenekim didnโt help when they statistically proved that he might have been onto something with all that de-coupling and team-alignmentโฆ)
Software architecture is in crisis, and the way to fix it is a hefty dose of anarchy.
(Admittedly, @nicolefv, @jezhumble and @realgenekim didnโt help when they statistically proved that he might have been onto something with all that de-coupling and team-alignmentโฆ)
I think he saved us; bringing us back to the path of value-delivery and independent services, but now with added independent teams.
(See https://t.co/B2hWmXhIqe if you need convincing)
*Shudder*
And consequently many, many #microservices adoptions failed; with #microservices themselves getting an undeserved bad name in the process.
What we need is a workable way to approach them, and in the process realise the associated benefits of both team autonomy and improvements in system architecture.
Iโll describe what it is and you could do it. Hopefully youโll see how it offers the best (only?) way out of this mess.
Straight away that means how we are used to doing architecture, via all-powerful architects taking all the decisions, is going to have to stop.
\u201cYou may think in describing anarchism as a theory of organisation I am propounding a deliberate paradox: \u2018anarchy\u2019 you may consider to be, by definition, the _opposite_ of organisation. In fact, however, \u2018anarchy\u2019 means the absence of government, the absence of _authority_. ..."
— Andrew Harmel-Law \U0001f3e1 (@al94781) November 29, 2020
(As @Grady_Booch has said โarchitecture represents the set of significant design decisions that shape the form and the function of a system, where significant is measured by cost of change.โ)
So the first test is can an #AnarchisticArchitecture deliver on this?
The answer is "Yes".
More from Software
Kubernetes vs Serverless offerings
Why would you need Kubernetes when there are offerings like Vercel, Netlify, or AWS Lambda/Amplify that basically manage everything for you and offer even more?
Well, let's try to look at both approaches and draw our own conclusions!
๐งตโฌ
1๏ธโฃ A quick look at Kubernetes
Kubernetes is a container orchestrator and thus needs containers to begin with. It's a paradigm shift to more traditional software development, where components are developed, and then deployed to bare metal machines or VMs.
There are additional steps now: Making sure your application is suited to be containerized (12-factor apps, I look at you: https://t.co/nuH4dmpUmf), containerizing the application, following some pretty well-proven standards, and then pushing the image to a registry.
After all that, you need to write specs which instruct Kubernetes what the desired state of your application is, and finally let Kubernetes do its work. It's certainly not a NoOps platform, as you'll still need people knowing what they do and how to handle Kubernetes.
โฌ
2๏ธโฃ A quick look at (some!) serverless offerings
The offer is pretty simple: You write the code, the platform handles everything else for you. It's basically leaning far to the NoOps side. There is not much to manage anymore.
Take your Next.js / Nuxt.js app, point the ...
Why would you need Kubernetes when there are offerings like Vercel, Netlify, or AWS Lambda/Amplify that basically manage everything for you and offer even more?
Well, let's try to look at both approaches and draw our own conclusions!
๐งตโฌ
1๏ธโฃ A quick look at Kubernetes
Kubernetes is a container orchestrator and thus needs containers to begin with. It's a paradigm shift to more traditional software development, where components are developed, and then deployed to bare metal machines or VMs.
There are additional steps now: Making sure your application is suited to be containerized (12-factor apps, I look at you: https://t.co/nuH4dmpUmf), containerizing the application, following some pretty well-proven standards, and then pushing the image to a registry.
After all that, you need to write specs which instruct Kubernetes what the desired state of your application is, and finally let Kubernetes do its work. It's certainly not a NoOps platform, as you'll still need people knowing what they do and how to handle Kubernetes.
โฌ
2๏ธโฃ A quick look at (some!) serverless offerings
The offer is pretty simple: You write the code, the platform handles everything else for you. It's basically leaning far to the NoOps side. There is not much to manage anymore.
Take your Next.js / Nuxt.js app, point the ...
You May Also Like
"I really want to break into Product Management"
make products.
"If only someone would tell me how I can get a startup to notice me."
Make Products.
"I guess it's impossible and I'll never break into the industry."
MAKE PRODUCTS.
Courtesy of @edbrisson's wonderful thread on breaking into comics โ https://t.co/TgNblNSCBj โ here is why the same applies to Product Management, too.
There is no better way of learning the craft of product, or proving your potential to employers, than just doing it.
You do not need anybody's permission. We don't have diplomas, nor doctorates. We can barely agree on a single standard of what a Product Manager is supposed to do.
But โ there is at least one blindingly obvious industry consensus โ a Product Manager makes Products.
And they don't need to be kept at the exact right temperature, given endless resource, or carefully protected in order to do this.
They find their own way.
make products.
"If only someone would tell me how I can get a startup to notice me."
Make Products.
"I guess it's impossible and I'll never break into the industry."
MAKE PRODUCTS.
Courtesy of @edbrisson's wonderful thread on breaking into comics โ https://t.co/TgNblNSCBj โ here is why the same applies to Product Management, too.
"I really want to break into comics"
— Ed Brisson (@edbrisson) December 4, 2018
make comics.
"If only someone would tell me how I can get an editor to notice me."
Make Comics.
"I guess it's impossible and I'll never break into the industry."
MAKE COMICS.
There is no better way of learning the craft of product, or proving your potential to employers, than just doing it.
You do not need anybody's permission. We don't have diplomas, nor doctorates. We can barely agree on a single standard of what a Product Manager is supposed to do.
But โ there is at least one blindingly obvious industry consensus โ a Product Manager makes Products.
And they don't need to be kept at the exact right temperature, given endless resource, or carefully protected in order to do this.
They find their own way.
