There are a lot more but these are the principal considerations that allow health and maintenance without headache.

- Boundaries must consider
> Downstream ecosystem
> Coupling level
> Business Criticity & Cohesion

- Rendering must consider
> Component Priority
> Graceful Degradation
> Fallback Strategy

- Decomposition must be aligned with:
> Organizational structure
> Deployment strategy
> Versioning Strategy

We also share a vision about Lock-In and portability to share insights about the principal mindset shift when moving to any technology and new ecosystem.

Knowing the tech journey is long, and we get back to zero all the time behind tech revolutions, We dive into HPC (High-Performance Computing) and HTC(High-Throughput Computing) to give more insights about what exactly makes different choices in software.

We dive into the Agronomy of Traditional and Serverless Solutions and look at them from Operational and Organizational perspectives.

In my Personal life, if i have a discussion, we need to decide rapidly, otherwise, I need all those details again, because my implemented event sourcing is not well designed.
😊 😊 😊

For occasional moments when I'm engaged to be early in the morning, I move to provisioned from on-demand. while in on-demand mode, neither an alarm (Cloudwatch events) can warm me up.

My holidays 🏖️ are mostly synchronous with some hour latencies ⏳ but well-serving (The family finally has fun 🙋‍♀️ ).
I have some downtime 🧨 early in the morning, and I don't well scale up before 9 AM, but i also have difficulties scaling down at night 🌃 🌙 .

I just said the same
Wow ,.......

This is why I find SQS the most scalable AWS service

Good Instrumentation allows to extract KPIs and have context , software, and process level Insights.

#software #logging #monitoring #observanility