DevOps is about Anti-fragility not only about OPS

The IT-industry always got 1 thing of of 10 and just because they have 1 thing they think they got the point. I saw this with SOA, REST, Agile and now DevOps is happening too.

Yes i will say one more time that the DevOps team is wrong. Is so wrong, is not just a name and is not just a matter of practices.

More and more a see what the it industry got from DevOps is CLOUD and Automation - witch is great because this a very important aspects of devops but however devops is way more than that.

The confusion a SEE is calling OPS -> DevOps, OPS is OPS, OPS is not DevOps. You have Dev in your company a most likely have a ITIL shared OPS in your company so lets say you have 100 developers mostly you have 20 DBAs.

Cloud and Automation => Deploys

Yes Deploys matters but is not only about that. I`m not saying automation is easy in fact is hard and takes lots of time and hard work - thats might be a reason why see so much devops teams or devops people or devops engineers. Because we have a very specialized work to get done around cloud and automation and people(developers) are too busy coding they cant afford stop so what people do? Get a DevOps team to carry all automation and cloud work.

The main problem this is creates is you just created a SILO and now this silo is not called OPS is called DevOps, Whats the difference from this SILO to your old OPS doing shared ITIL and lots of process and slow deploys? Well of course automation and cloud have value but this just means you can do better OPS it does not means you are doing DevOps. When you got specialized - Certifications are the next step and this already start happening.

Better and modern OPS is very important dont get me wrong, we all need Agile Operations and Cloud and Immutable Infrastructure and Discoverability and Centralized Logging and So many other important aspects.

The Issues with SILOs?

SILOs are very anti-lean idea. Often they are full of waste because of each silo has his owen set of priorities and goals not to mention classical lean wastes like hand offs, delays, bottlenecks, motion, extra steps, and so on and on... DevOps should be driven by Lean principles and thats a great reason to not do a silo. The main issues is all companies what benefits but they really dont want to HARD changes well guess what? No Pain No Gain. Our industry is not ready to DevOps. In other hand i dont think we was ready for agile or soa, why it get it all wrong always? Lots of companies are moved by Hypes or gartners charts. Several times this kinda of hype goto a kinda of standard Strategics planing and become a KPI them people need do something. DevOps or Agile or SOA or Scrum should never be Strategic Goals - Make you business better should be a reality to live by everyday. People have the vision that if you put something as an Strategic Goals magic happens actually thats not true - most of times this is like a game and when you have a game cheating is built in feature.

Having a clear and right vision is everything - this is so hard and so few people get it right. That`s why is so hard and that will dont stop until we fix the right root causes deep down to the people who make calls or lead.

DevOps is About Anti-fragility

Whats is anti-fragility ? It is better Software. You start doing all sets of new aspects about your development and operation that you never did it before like:
  * Stress Testing
  * Caos Testing
  * Failure Injection Testing
  * A Service Always can recover from disters
  * Bugs or Failures dont tear down your service - how ever you can degrades the user experience
  * Fall back Mechanisms
  * Proper re-trys and Timeouts
  * Fail over / Dynamic Partitioning
  * Centralized Logging
  * Request control (know what users asked - when and how things blow)
  * Continuous Performance Improvement
  * Incident Training
  * Automated Roll backs
  * Proper Data Management - Automation on DB, CQRS, Compensation, etc...
  * Reactiveness
  * SOA / Microservices right principles and governance
  * Metrics, Scientific Approach to find and improve things
  * Better Data Centers, Internal PaaS and Mesos
  * Awesome Monitoring Proper Postmortems

You only can have that if you dev and ops work together looking for this aspects and Dev needs to know OPS and OPS need to know Dev, they really need to understand the services otherwise you are not doing devops. Easily you could be doing better OPS or modern ops with Automation and Cloud but todo DevOps you need Culture you need a team working together to make sure your software is anti-fragile.

Cheers,
Diego Pacheco



Popular posts from this blog

Kafka Streams with Java 15

Image
Kafka Streams is a Streaming library similar to Spark and Flink which works with Apache Kafka. Kafka stream can be useful to process historical and near-real-time big data workloads but also for non-realtime analytical computations at scale for the online world as well. Kafka-Streams is elastic, highly scalable, fault-tolerant, and fully integrated with Kafka. You can use Kafka Stream with Java, Scala, Kotlin JVM applications and also have exactly-once processing semantics. Kafka-Streams is being used by the New York Times, Pinterest, Line, Trivago, Zalando, and many other companies. Today I want to share a video of Kafka-Streams running with Kafka 2.6 and Java JDK 15. So Let's get started. 
read more »

Rust and Java Interoperability

Image
Rust does not stop for one second to amaze me. It looks like Rust was designed to talk to every other language so easily. No kidding, it's clear way Web Assembly and rust have lots in common. Java is never an easy lang to interop with. Today I will show how easily we can interop Java & Rust. In order to do so, we will need to use the Java and Rust compilers. For Java, we will not require any other lib than the standard JDK. For Rust, we will need to create a lib project in cargo and we will need to use the crate JNI. I love this feature because java does not allow low-level code on the main language. So if we need to do something low level, efficiently Rust is my first choice, not only for safety reasons but because is really fast.  Let's get started.
read more »

HMAC in Java

Image
In 2018 AWS CTO(Vogels) said : "Security is everyone's job". For the last 2 years, there was so many famous and big data leaks and breaks that made that statement be very true more than ever. Security often could mean worst performance and worst user experience so in order to get it right you really need to think about the designs before jumping into to code and consider performance and user experience has main requirements.  I was thinking about writing about how to do HMAC in Java for a while and recently Redis 6.0.0 come out and to my surprise, there was a refactoring on the password part in order to use HMAC.  Security easily could scare engineers often because it is not something well spread yet but I believe this will change soon. It does not matter if you have to deal with PII Data or not, security is super relevant because everybody is running their workloads at the cloud or with IoT and Edge devices which means more distribution, more code, more points of fail
read more »