Should’ve edited audio. Good info though

Fuck you thoughtworks for inventing your stupid tech radar. It caused me to having to stop programming in Purescript. Because some fucking idiots think Java is an acceptable PL

Great job! I find 37% to be exciting and motivating; And this is with today's models and the most naive prompting approaches.

👍👍👍 very good

Rust is definitely not hype, already has very serious mainstream traction. Zig certainly has the potential, but not serious mainstream adoption (yet!). Zig is definitely not hype. Carbon, I like the idea of it, but it's in extremely slow development. I think it's going to miss its window of opportunity. So I wouldn't necessarily call Carbon hype, it will just be a Johnny-come-lately to the party and probably therefore not see widespread adoption, if and when it's even finished.

Rust is too messy, zig ftw!

Great presentation. I have many questions to how implement Data Mesh in organization. How can I contact with you? Thank you!

Have you ever consider how much carbon dioxide a human can breathe out every day? This whole carbon footprint thing is complete nonsense. Please focus your energy on doing actually good stuff for humanity. Not something sounds good but evil.

🎯 Key Takeaways for quick navigation: 02:17 *🏗️ Modern architecture involves difficult tradeoff analysis, necessitating new tools and practices beyond traditional heavyweight frameworks like ATAM and CBAM.* 04:47 *📚 "Architecture-- The Hard Parts" book focuses on dissecting complex problems in software architecture, particularly in distributed systems, to understand and mitigate their difficulty.* 06:13 *🔄 Modern tradeoff analysis involves identifying coupled components, analyzing their interdependencies, and assessing tradeoffs to understand the impact of changes.* 09:36 *🛠️ Breaking down applications into smaller distributed components enhances maintainability, testing, deployment, scalability, fault tolerance, and operational characteristics.* 13:26 *🧱 Tactical forking offers a method to break down monolithic applications by cloning the entire codebase and gradually removing unnecessary parts, though it may result in less elegant outcomes.* 16:50 *🎯 Consider both domain analysis and architecture characteristics to determine whether a monolithic or distributed architecture is suitable, based on the complexity of the system's requirements.* 20:15 *🔄 Architectural quantum, defined as an independently deployable component with high functional cohesion, aids in analyzing and improving the evolvability of architecture topologies.* 22:37 *🧩 Static versus dynamic coupling is an essential distinction in architecture analysis, impacting the scalability and performance of architectural components.* 24:34 *🔗 Microservice architectures lead to distinct quanta, with each service forming its own quantum if decoupled from others.* 25:32 *🧩 Static quantum in architecture includes all dependencies required to bootstrap a service, providing a view of the architecture's wiring and integration points.* 27:54 *🔄 Consistency, communication (synchronous vs. asynchronous), and coordination (orchestration vs. choreography) are fundamental forces in distributed architectures, affecting each other when changed.* 31:42 *🛠️ Static coupling concerns the granularity of services in microservice architecture, balancing disintegrators (breakdown) and integrators (bundling) to achieve optimal service size.* 37:53 *💡 Volatility is one aspect to consider when decomposing services, but it shouldn't be the sole driver as other factors like scalability, fault tolerance, and security are equally important.* 40:13 *📊 Integrators like database transactions and data dependencies help determine the optimal boundaries of services, preventing overly fine-grained architectures that require complex stitching.* 46:36 *🧰 Bundling overly fine-grained services back together can alleviate workflow and performance issues, demonstrating the importance of considering communication patterns and service granularity in architecture design.* 50:01 *⚖️ Synchronous calls in distributed architectures like microservices can lead to performance issues and synchronization problems between services, impacting reliability.* 51:22 *🔄 Asynchronous communication in distributed architectures, such as using message queues, provides flexibility and allows handling differences in scale and performance between services, leading to a more reliable and less brittle architecture.* 54:18 *📊 Orchestration involves a mediator component coordinating workflows, suitable for complex workflows, error handling, and state management, while choreography decentralizes coordination but can become complex, especially with error handling.* 57:42 *🔀 Choreography offers better responsiveness, scalability, and decoupling, while orchestration excels in workflow control, error handling, and state management, requiring trade-offs between the two based on project requirements.* 01:02:59 *🔄 Different architectural patterns, such as saga patterns, offer varying levels of coupling, complexity, responsiveness, and scalability in distributed systems, highlighting the importance of careful architectural decisions based on project needs.* 01:07:40 *🔗 Eventual consistency, asynchronous communication, and orchestration provide a balance between complexity and scalability in microservices architectures, offering high scalability and ease of understanding.* 01:13:58 *📊 Quantitative analysis is challenging for architectures due to their unique nature, but qualitative analysis, such as assessing values and creating matrices, can reveal important insights.* 01:14:55 *🔄 Iterative design in distributed architectures involves qualitatively understanding the impact of different solutions on each other, facilitating the creation of tradeoff matrices.* 01:17:22 *🛡️ Building an architectural fitness function is crucial during architectural restructuring to prevent breaking functionality across components and maintain structural integrity.* 01:18:51 *⏰ Responsiveness is context-dependent; while critical in certain scenarios like high-frequency trading, it may be less important in others such as casual apps, highlighting the need for individualized assessments.* 01:20:19 *🤝 Preventing tight coupling between teams in distributed architectures is essential for scalability and agility, emphasizing the importance of avoiding excessive reuse and promoting abstraction.* 01:24:06 *📈 Metrics like cyclomatic complexity and distance from the main sequence offer holistic views of codebase quality, aiding in decision-making regarding architectural changes based on organizational goals and strategic importance.* Made with HARPA AI

i hope i live to see zig win but im interested in try carbon coz ive alr tried rust

AWS Datazone?

Very practical discussion, I have personally been through it and have made mistakes :). Where do we find the catalog discussed in podcast, can anyone share link.

อาจารย์ อนุชิต พูดได้สนุกมากเลยครับ

I recommend ignoring carbon until it's actually available

Informative !!

Awesome presentation !!

Too bad they're basically nazis

this channel posts 90% trash

That's inspiring and insightful!

Do we have access to the 4k hours of dataset, you mentioned in the presentation ?

Believe in yourself and your dreams. With a positive mindset and determination, you can achieve anything you set your mind to.

Thanks for this. Learn about the need of growing the business gradually and don't rush in recruiting many people when the business can't sustain them. Incremental growth

As I already built my own schema system the fist thing that came into my mind after rule libraries is serialisation.

Bravo, Sabrina and Nina! Excellent presentation.

How to join?

This is excellent work!

trying not to be racist but man!! boon?? 😣

Proud to be on his team.

A valuable insight into the infrastructure needed to make the experience exceed expectations. Well done.

ZICK dude!

The obvious language that wasn’t mentioned was Herb Sutter’s cppfront, which implements a new syntax for C++, giving 100% compatibility and much greater safety.

Guys please, if the man can't even speak English in a reasonable way - just publish an article or use a proxy - FFS, the point is to share information / raise awareness/engagement - if I were sitting in that room I would have checked out before the man said "BOON" (bun). Nothing against him it just happens too much, f**k - just write an article next time.

It never disappoint us.. as expected, the AI based blips and the importance given to this edition is much helpful...👍

Very nice presentation. More people should watch this.

Whenever I hear "no runtime" for Rust, I think "well..." 🙂 I mean there's a panic handling stack, a bounds checker, ... and probably a bunch of other things baked into the binary.

Hi

Whoever has edited this video is not very bright. Why do I have to look at the back of the attendance heads when the lecturer is explaining an example on the board?

00:01 Quality assurance with continuous delivery 02:51 Challenges with automated testing 08:55 Automated tests are expensive and slow to run 11:47 Fast feedback is crucial for test-driven development (TDD). 16:35 Running automated tests before code check-in is crucial for preventing problems. 18:47 Continuous integration and decoupled architecture for continuous delivery 23:01 Ensure components are well-tested for effective communication 25:03 The goal of quality assurance is to reduce risk and impact on user satisfaction. 29:59 Ways to reduce risk in continuous delivery 32:56 Following continuous delivery practices can reduce risk and reliance on end-to-end tests. 37:44 Reducing risk by testing smaller changes and isolating impact. 39:48 Reduce testing by visualizing and reducing risk. 43:53 Continuous delivery infrastructure as code promotes clean systems and less reliance on manual knowledge 46:23 Cultural changes are crucial for ensuring quality. 51:00 Code should be treated as a hypothesis until it's in production 53:14 Efficiency in manual testing through time manipulation 57:45 Organizations can build their own radar for tool techniques. 59:57 Companies that succeed with continuous delivery have a clear direction and back it up with resources. 1:04:32 Dependence on browser-based automated tests and the need for continuous delivery.

Zig

Loved this. Its inspiring to hear from other leaders. I needed to hear this.

Great Video, think this needs more attention!

Thanks in advanced

Special thanks for captions/subtitles!! Sometimes it is hard to understand the said words.

Oh wow, this is re-upload with the full version? It was previously just 20 minutes long as I remember

where you got this data for mesh ?

Great stuff and yes @rita Arrigo we must get diverse stakeholders engaged in AI design process