Nature: A way to think!

Thats a very interesting thing to think about it. As a software architect i`m always trying to understand the nature of the things.

For a system, you could have some systems that are more sensible to latency or CPU BOUND or Memory Bound or could have other dimensions.

They could be Data Driven or Domain / Behavior Centric or event event centric. If you think about what goes on the system like cars the are driven in a specific road, if you think thought this properties you can think as tickets and them you could have very slow care like trucks or fast sport cars, i would call this ticket profile so you could have fast running jobs or long running jobs.

Solutions / frameworks / libraries are made for specifics natures. Like a sea fish or river fish or urban fish :-)  All same fix but at the same time all diferent ones.

People tend to just see software are BEST at the very moment and often dont think about the properties of the system they are dealing with. If you can understand they system you are dealing with you can be in a better spot the make a call or make a architecture thats really scale out.

The Dimensions

I`m still working through this but i see some things we could use to classify systems or modules or SOA Services. IMHO would be something like this:

* Centric Nature: Data, Behavior/Rules, Process/Task, IO
* Ticket: Short Running Job, Long Running Job
* Mode: Online, Off Line
* Profile: CPU Bound, IO Bound, Latency Driven, Memory Driven
* Main Architecture: Request Driven, EDA, Pub/Sub, SEDA, Actors, Stream, Batch
* Distribution: Standalone, Cluster, P2P

And much and much more, but if you think about this you will be in a way better spot to realize what to do. Software architecture is just a mirror of the real business thats why requirements are so important. You need to understand where you are going and what could happen next so you will cover the aspect to make sure that your development scales(more team) and also your number of user or requests.

Architecture or Signal Repeater?

A Real software architecture will compose components, ideias, principles and libraries/frameworks in a very specific way to make sure you do the right FIT solution for you problem domain. Unfortunately people just go to the infoq shop and get the latest buzzword and start apply on they system and they call this update or technical improvement,

The main problem with that is that you dont tackle the real problems. Potentially you could burn lots of hours, energy and money on the wrong things the problem in that in the future you night not have they money(you may regret it).

Think about the Problem domain

As more as you think about the problem domain in sense of understand how it behaves, what are they boundaries, what are the constraints, what are the real limitations more you will be able to pick the right architecture set. This is all about decision making, to make better decisions you need to have a great idea about the problem but also about the options for the solution landscape.

Cheers,

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 »