chore: sync content to repo (#10210)

Co-authored-by: nilbuild <4921183+nilbuild@users.noreply.github.com>

Author: github-actions[bot]

roadmaps/software-architect/content/acid-cap-theorem@bbKEEk7dvfFZBBJaIjm0j.md

@@ -1,10 +1,6 @@
-# ACID & CAP Theorem
-
-ACID (Atomicity, Consistency, Isolation, Durability) and CAP (Consistency, Availability, Partition Tolerance) are essential concepts in distributed systems. They are often used to explain the trade-offs between consistency and availability.
-
-CAP is an acronym for Consistency, Availability, and Partition Tolerance. According to the CAP theorem, any distributed system can only guarantee two of the three properties at any time. You can't guarantee all three properties at once.
-
-ACID is an acronym that stands for Atomicity, Consistency, Isolation, Durability. ACID is a set of properties of database transactions intended to guarantee validity even in the event of errors, power failures, etc.
+# ACID, CAP Theorem
+ 
+ACID describes the guarantees a database transaction provides: atomicity, consistency, isolation, and durability, ensuring reliable operations even under failure. The CAP theorem states that a distributed system can only guarantee two of three properties at once: consistency, availability, and partition tolerance. Architects use both concepts to reason about the trade offs involved in choosing databases and designing distributed systems.
 
 Visit the following resources to learn more:
 

roadmaps/software-architect/content/apache-spark@a0baFv7hVWZGvS5VLh5ig.md

@@ -1,8 +1,7 @@
 # Apache spark
 
-Apache Spark is a multi-language engine for executing data engineering, data science, and machine learning on single-node machines or clusters.
+Apache Spark is a distributed data processing engine that performs computations in memory, making it significantly faster than earlier tools like MapReduce for many workloads. It supports batch processing, streaming, machine learning, and graph processing through a single unified framework. Architects often choose Spark for large scale analytics pipelines that need both speed and flexibility.
 
 Visit the following resources to learn more:
 
-- [@official@Apache Spark](https://spark.apache.org/)
-- [@feed@Explore top posts about Apache](https://app.daily.dev/tags/apache?ref=roadmapsh)
+- [@official@Apache Spark](https://spark.apache.org/)

roadmaps/software-architect/content/apis--integrations@Ocn7-ctpnl71ZCZ_uV-uD.md

@@ -1,6 +1,6 @@
 # APIs and Integrations
 
-APIs (Application Programming Interfaces) are essential for enabling communication between different software applications, allowing them to share data and functionality seamlessly. They serve as the bridge that connects disparate systems, making it possible for applications to interact without needing to know the internal workings of one another. Integration, on the other hand, refers to the process of connecting these systems to work together effectively, often utilizing APIs to facilitate data exchange and process automation. By leveraging APIs in integrations, organizations can enhance operational efficiency, reduce data silos, and improve user experiences through seamless data flow between applications.
+APIs and integrations define how different systems and services communicate with each other, whether within a company or across organizations. Choosing the right integration style, protocol, and data format affects performance, flexibility, and how easily new systems can be connected later. This is a core concern in almost every modern architecture, since few systems operate in isolation.
 
 Visit the following resources to learn more:
 

roadmaps/software-architect/content/application-architecture@Lqe47l4j-C4OwkbkwPYry.md

@@ -1,6 +1,6 @@
-# Application Level Architecture
-
-The lowest level of architecture. Focus on one single application. Very detailed, low level design. Communication is usually within one development team.
+# Application Architecture
+ 
+Application architecture focuses on the internal structure of a single software application: its modules, layers, and the patterns used to organize code. It determines how the application handles concerns like data access, business logic, and user interface separation. Decisions made here affect how easy the application is to test, extend, and maintain over time.
 
 Visit the following resources to learn more:
 

roadmaps/software-architect/content/atlassian-tools@3bpd0iZTd3G-H8A7yrExY.md

@@ -1,8 +1,6 @@
 # Atlassian Tools
-
-Atlassian tools offer a suite of solutions designed to streamline collaboration, project management, and incident handling for various teams. Jira serves as the core workflow engine, allowing organizations to track tasks through customizable workflows with granular permissions. Specialized tools like Jira Service Desk cater to help desk teams for managing incoming requests, while Jira Core enables business teams to organize and execute task-oriented projects across departments like marketing, HR, and operations. For enhanced collaboration, Confluence acts as a knowledge-sharing wiki, allowing teams to create, share, and audit content changes seamlessly. Bitbucket provides Git repository management for enterprise teams, fostering efficient collaboration on codebases.
-
-Other tools cater to more specific needs. **Statuspage** focuses on communication during outages or maintenance, keeping users informed from investigation to resolution. **Opsgenie** ensures smooth incident management for always-on services, helping dev and ops teams stay in control of alerts. **Advanced Roadmaps** for Jira assists multiple teams in capacity planning and dependency tracking, while **Jira Align** supports enterprise-level agile planning to align strategy with execution and drive digital transformation. Together, these tools empower teams to improve efficiency, transparency, and adaptability across various workflows.
+ 
+Atlassian tools, including Jira and Confluence, support project tracking and documentation for software teams at scale. Jira manages tasks, sprints, and issues in agile workflows, while Confluence stores documentation and design discussions. Many enterprise teams standardize on these tools for both day to day work tracking and long term knowledge management.
 
 Visit the following resources to learn more:
 
@@ -13,5 +11,4 @@ Visit the following resources to learn more:
 - [@official@Statuspage](https://www.atlassian.com/software/statuspage)
 - [@official@Opsgenie](https://www.atlassian.com/software/opsgenie)
 - [@official@Advanced Roadmaps for Jira](https://www.atlassian.com/software/jira/features/roadmaps)
-- [@official@Jira Align](https://www.atlassian.com/software/jira/align)
-- [@feed@Explore top posts about Atlassian](https://app.daily.dev/tags/atlassian?ref=roadmapsh)
+- [@official@Jira Align](https://www.atlassian.com/software/jira/align)

roadmaps/software-architect/content/auth-strategies@KiwFXB6yd0go30zAFMTJt.md

@@ -1,18 +1,6 @@
-# Authentication Strategies
-
-Authentication strategies are essential for ensuring secure access to applications and systems. They define how users are verified before being granted access to resources. Here are some common authentication strategies:
-
-Password-Based Authentication
-
-Multi-Factor Authentication (MFA)
-
-OAuth and OpenID Connect
-
-Token-Based Authentication:
-
-Biometric Authentication
-
-Certificate-Based Authentication
+# Auth Strategies
+ 
+Authentication and authorization strategies determine how a system verifies who a user is and what they are allowed to do. Common approaches include session based authentication, token based methods like JWT, and protocols like OAuth for delegated access. Choosing the right strategy affects both security and how easily a system integrates with other services.
 
 Visit the following resources to learn more:
 

roadmaps/software-architect/content/babok@LQlzVxUxM3haWRwbhYHKY.md

@@ -5,4 +5,4 @@ The guide to the Business Analysis Body of Knowledge (BABOK Guide) is a book fro
 Visit the following resources to learn more:
 
 - [@official@Babok](https://www.iiba.org/career-resources/a-business-analysis-professionals-foundation-for-success/babok/)
-- [@article@Wikipedia](https://en.wikipedia.org/wiki/A_Guide_to_the_Business_Analysis_Body_of_Knowledge)
+- [@article@A Guide to the Business Analysis Body of Knowledge](https://en.wikipedia.org/wiki/A_Guide_to_the_Business_Analysis_Body_of_Knowledge)

roadmaps/software-architect/content/balance@otHQ6ye1xgkI1qb4tEHVF.md

@@ -1,6 +1,6 @@
 # Balance
-
-Achieving balance in architecture requires managing trade-offs between quality, cost, and development speed, avoiding over-engineering while aligning functional and non-functional requirements. Architects must navigate conflicting goals, like balancing short-term simplicity with long-term vision, ensuring solutions fit future needs while involving developers, businesses, and managers in understanding the financial and strategic impact. Additionally, architects often mediate between diverse groups, resolving conflicts and aligning strategies through effective communication, such as the “Four-Ears Model” by Schulze von Thun, which aids in fostering collaboration and achieving balanced, strategic outcomes.
+ 
+Balance refers to weighing competing priorities such as speed versus quality, or innovation versus stability. An architect regularly makes trade offs between what is technically ideal and what is practical given time and budget constraints. Finding the right balance keeps a project moving without accumulating excessive technical debt.
 
 Visit the following resources to learn more:
 

roadmaps/software-architect/content/bpm-bpel@DwNda95-fE7LWnDA6u1LU.md

@@ -1,19 +1,6 @@
 # BPM BPEL
 
-BPM: Business Process Management
---------------------------------
-
-Medium or large enterprises needs robust processes to streamline their business needs by reducing the cost incurred per process and diminishing the turn around time for each activity. To achieve the above, there are various BPM tools like PEGA, IBM BPM, Appian, etc. Basically these tools automate the processes through a robust process modelling and implementation.
-
-BPMN: Business Process Management Notations
--------------------------------------------
-
-Its is a standard for representing business processes graphically. While modelling the process, the notations used are complied with BPMN (there are other like EPC, etc.). So BPMN is a standard notation that BPM consultants follow to model the business process. BPMN has versions and now BPMN 2.0 is the standard one.
-
-BPEL : Business Process Execution Language
-------------------------------------------
-
-Programmers use BPEL to define how a business process that involves web services will be executed. BPEL messages are typically used to invoke remote services, orchestrate process execution and manage events and exceptions. BPEL is often associated with Business Process Management Notation. In many organizations, analysts use BPMN to visualize business processes and developers transform the visualizations to BPEL for execution.
+Business process management describes methodologies and tools for modeling, automating, and optimizing business processes across an organization. BPEL, the Business Process Execution Language, is an XML based language used to define and orchestrate these processes, often within service oriented architectures. Architects working on enterprise workflow automation need to understand how BPM tools coordinate multiple systems to complete a business process.
 
 Visit the following resources to learn more:
 

roadmaps/software-architect/content/client--server@mka_DwiboH5sGFhXhk6ez.md

@@ -4,5 +4,4 @@ Client-server architecture is a computing model that separates tasks or workload
 
 Visit the following resources to learn more:
 
-- [@article@What is Client-Server Architecture](https://www.simplilearn.com/what-is-client-server-architecture-article)
-- [@feed@Explore top posts about Architecture](https://app.daily.dev/tags/architecture?ref=roadmapsh)
+- [@article@What is Client-Server Architecture](https://www.simplilearn.com/what-is-client-server-architecture-article)