You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-[Azure Well-architected Framework :WAF](https://learn.microsoft.com/en-us/azure/well-architected/): workload-focussed design and continuous improvement guidance
61
61
-[Azure Architecture Center :AAC](https://learn.microsoft.com/en-us/azure/well-architected/service-guides/?product=popular): architecture patterns and reference architectures
62
+
-[Best practices in cloud applications](https://learn.microsoft.com/en-us/azure/architecture/best-practices/index-best-practices)
- Abstractly speaking, a landing zone helps you plan for and design an Azure deployment, by conceptualizing a designated area for placement and integration of resources. There are two types of landing zones:
66
+
1.`platform landing zone`: provides centralized enterprise-scale foundational services for workloads and applications.
67
+
2.`application landing zone`: provides services specific to an application or workload.
- DevOps, Platform engineering and SRE (site reliability engineering) [ref](https://www.splunk.com/en_us/blog/learn/sre-vs-devops-vs-platform-engineering.html)
236
277
@@ -305,7 +346,7 @@ This mindmap created by `https://app.mindmapmaker.org/`
305
346
306
347
<summary>SSO workflow, Types of SSO, SSO Implementations</summary>
307
348
308
-
🔹SSO workflow: Identoty Provider (IdP), Service Provider (SP), SSO Server
349
+
🔹SSO workflow: Identity Provider (IdP), Service Provider (SP), SSO Server
309
350
- IdP: Central Authentication server e.g., Google
310
351
- SP: Individual Applications rely on SSO e.g, Trello
311
352
- SSO Server: Bridge between IdP and SPs
@@ -324,5 +365,47 @@ This mindmap created by `https://app.mindmapmaker.org/`
324
365
325
366
🔹SSO Implementations: Microsoft Entra ID (FKA Micorsoft Active Directory), Okta, Ping Identity, OneLogin, Auth0
326
367
368
+
</details>
369
+
370
+
- Deployment Styles: Blue/Green, Canary, and A/B
371
+
372
+
<details>
327
373
374
+
<summary>Blue/Green, Canary, A/B</summary>
375
+
376
+
🔹Blue/Green Deployment: Two identical environments, "Blue" and "Green". Deploy new version in inactive environment, test, then switch users to it. For example, AWS supports blue/green deployment strategies including Elastic Beanstalk, OpsWorks, CloudFormation, CodeDeploy, and Amazon ECS.
377
+
378
+
🔹Canary Deployment: Roll out new version to a small group of users, monitor feedback, then do a full-scale release.
379
+
380
+
🔹A/B Testing: Compare two versions of a webpage or app to see which performs better. A typical example of A/B testing is website usability testing.
381
+
382
+
</details>
383
+
384
+
- Flaky Test: A Flaky Test is a test that sometimes passes and sometimes fails, despite no changes in the code. Causes can include poorly written tests, async waits, test order dependency, and concurrency issues. They can slow down CI/CD pipelines and cause issues for end users. [ref](https://github.com/jmicco/JaSST_tutorial)
385
+
386
+
- Hadoop Ecosystem
387
+
<details>
388
+
<summary>Hadoop vs Azure, AWS, GCP</summary>
389
+
390
+
🔹1. **HDFS (File Storage)**: Azure Data Lake Storage, Amazon S3, Google Cloud Storage
391
+
392
+
🔹2. **YARN (Resource Management)**: No direct equivalent in Azure, AWS, GCP
393
+
394
+
🔹3. **MapReduce (Data Processing)**: HDInsight, Amazon EMR, Google Cloud Dataproc
395
+
396
+
🔹4. **Spark (Fast Data Processing)**: Databricks, Spark in HDInsight, Azure Synapse Analytics, Amazon EMR, Google Cloud Dataproc
0 commit comments