<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Adarsha Jha on Medium]]></title>
        <description><![CDATA[Stories by Adarsha Jha on Medium]]></description>
        <link>https://medium.com/@adarshajha14?source=rss-69243003cf04------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*6JOirOH84IO11Qaz1SGfag.jpeg</url>
            <title>Stories by Adarsha Jha on Medium</title>
            <link>https://medium.com/@adarshajha14?source=rss-69243003cf04------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 17:06:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@adarshajha14/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Build Entire Infrastructure from a Single Markdown File]]></title>
            <link>https://medium.com/@adarshajha14/build-entire-infrastructure-from-a-single-markdown-file-423f65f69641?source=rss-69243003cf04------2</link>
            <guid isPermaLink="false">https://medium.com/p/423f65f69641</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[infra]]></category>
            <category><![CDATA[markdown]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Adarsha Jha]]></dc:creator>
            <pubDate>Fri, 13 Feb 2026 07:40:39 GMT</pubDate>
            <atom:updated>2026-02-13T07:40:39.148Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>From documentation → running system</strong></p><p>Modern engineering teams struggle with a familiar problem: <strong>docs drift, configs scatter, and infra becomes hard to reproduce.</strong> What if your <em>documentation itself</em> could generate the entire working system?</p><p>This article explains how you can use <strong>a single Markdown file as the source of truth</strong> to automatically create a complete, runnable infrastructure — including backend APIs, database, Docker setup, and even Swagger docs.</p><h3>The Idea: “Infrastructure as Markdown”</h3><p>Instead of spreading logic across many files (code, configs, docs), you keep everything inside <strong>one Markdown file</strong>.</p><p>This file contains:</p><ul><li>Architecture spec</li><li>Environment config</li><li>API contract</li><li>Embedded file templates (code, Docker, configs)</li></ul><p>Then a simple script <strong>parses the Markdown and generates the entire project automatically</strong>.</p><p>So your workflow becomes:</p><pre>Edit Markdown → Run Script → Full Infra Ready</pre><h3>Why Markdown?</h3><p>Markdown is:</p><ul><li>Human-readable</li><li>Version-friendly (Git diffs cleanly)</li><li>Documentation-first</li><li>Portable across teams</li></ul><p>It becomes a <strong>single source of truth</strong> for both humans and machines.</p><h3>What Can Be Generated?</h3><p>From one .md file, you can generate:</p><ul><li>Backend service (e.g., Go / FastAPI / Node)</li><li>Database setup (Postgres, CouchDB, etc.)</li><li>Dockerfile + docker-compose</li><li>Swagger / OpenAPI docs</li><li>Environment config</li><li>Makefile / run scripts</li><li>Project structure</li><li>Health checks</li><li>Logging + production defaults</li></ul><p>Essentially, <strong>a fully runnable application stack</strong>.</p><h3>Architecture Flow</h3><pre>Markdown Spec<br>   ↓<br>Generator Script (parser)<br>   ↓<br>Creates Files + Code<br>   ↓<br>Build + Run (Docker / Make)<br>   ↓<br>Working Infrastructure</pre><h3>How It Works (Concept)</h3><h3>Step 1 — Write a Markdown Infra Spec</h3><p>The Markdown contains structured sections like:</p><ul><li>App config</li><li>Database</li><li>Resources / APIs</li><li>Docker setup</li><li>Embedded file templates</li></ul><p>It becomes both <strong>documentation and blueprint</strong>.</p><h3>Step 2 — Embed Files Inside Markdown</h3><p>You can embed real project files using special blocks like:</p><pre>```FILE:docker-compose.yml<br>services:<br>  api:<br>    build: .<br>  db:<br>    image: couchdb:3<br>```</pre><p>These blocks are extracted by the generator and written as real files.</p><h3>Step 3 — Generator Parses Markdown</h3><p>A small script (bash, Go, Python, etc.):</p><ul><li>Reads the Markdown</li><li>Extracts FILE: blocks</li><li>Writes them to disk</li><li>Substitutes variables (module name, ports, etc.)</li><li>Generates Swagger</li><li>Runs Docker</li></ul><h3>Step 4 — Run Everything</h3><p>You run just one command:</p><pre>./run.sh</pre><p>And the script:</p><ul><li>Generates full repo</li><li>Builds services</li><li>Starts containers</li><li>Opens working API + DB + Swagger</li></ul><h3>Real Example Stack</h3><p>Using this method, you can generate:</p><ul><li>Go REST API (CRUD)</li><li>CouchDB database</li><li>Swagger UI docs</li><li>Docker multi-stage build</li><li>docker-compose orchestration</li><li>Health endpoints</li><li>Graceful shutdown</li><li>Structured logging</li></ul><p>All from <strong>one Markdown file</strong>.</p><h3>Benefits</h3><h3>1. Single Source of Truth</h3><p>No config drift. Docs = system.</p><h3>2. Reproducible Infrastructure</h3><p>Anyone can rebuild the full system with one command.</p><h3>3. Faster Prototyping</h3><p>Spin up full backend infra in minutes.</p><h3>4. Self-Documenting Systems</h3><p>Architecture lives inside the Markdown.</p><h3>5. Great for AI-Driven Development</h3><p>AI tools can read Markdown and generate code reliably.</p><h3>6. Clean Version Control</h3><p>One file describes everything → easier reviews and diffs.</p><h3>When to Use This Approach</h3><ul><li>Bootstrapping new services</li><li>Internal platforms / scaffolding</li><li>Rapid backend prototypes</li><li>Teaching / architecture demos</li><li>Dev environments</li><li>Infra-as-code experimentation</li><li>AI-generated systems</li></ul><h3>Limitations</h3><ul><li>Not a replacement for Terraform / Kubernetes at scale</li><li>Needs a generator script</li><li>Requires disciplined Markdown structure</li><li>Large systems may need modularization</li></ul><p>But for <strong>service-level infrastructure</strong>, it’s extremely powerful.</p><h3>Extending the Idea</h3><p>You can expand this approach to:</p><ul><li>Multiple services</li><li>Multi-resource APIs</li><li>CI/CD generation</li><li>Kubernetes manifests</li><li>Helm charts</li><li>Observability stack</li><li>Multi-environment configs</li><li>Secrets handling</li><li>Code generation from schema</li></ul><h3>The Bigger Concept: Docs → Infra</h3><p>This pattern represents a shift:</p><p><strong>Documentation is no longer passive.<br> Documentation becomes executable.</strong></p><p>Markdown stops being just text — it becomes a <strong>machine-readable blueprint</strong> capable of generating real systems.</p><h3>Final Thoughts</h3><p>If your documentation can generate your infrastructure, you get:</p><ul><li>Reproducibility</li><li>Clarity</li><li>Speed</li><li>Simplicity</li></ul><p>And most importantly — <strong>a system that explains itself.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=423f65f69641" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Build a Full FastAPI + Postgres Infra Using a Single Markdown File]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-snippet">What if your entire backend infrastructure could be generated from a single .md file?</p><p class="medium-feed-link"><a href="https://medium.com/@adarshajha14/build-a-full-fastapi-postgres-infra-using-a-single-markdown-file-36ee8558b8ca?source=rss-69243003cf04------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@adarshajha14/build-a-full-fastapi-postgres-infra-using-a-single-markdown-file-36ee8558b8ca?source=rss-69243003cf04------2</link>
            <guid isPermaLink="false">https://medium.com/p/36ee8558b8ca</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[markdown]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Adarsha Jha]]></dc:creator>
            <pubDate>Fri, 13 Feb 2026 07:21:03 GMT</pubDate>
            <atom:updated>2026-02-13T07:21:03.281Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Kafka vs RabbitMQ vs AWS SNS: Key Differences Explained]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-snippet">In modern distributed systems and cloud-native architectures, messaging and event streaming play a crucial role. They enable applications&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@adarshajha14/kafka-vs-rabbitmq-vs-aws-sns-key-differences-explained-635a9b46029f?source=rss-69243003cf04------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@adarshajha14/kafka-vs-rabbitmq-vs-aws-sns-key-differences-explained-635a9b46029f?source=rss-69243003cf04------2</link>
            <guid isPermaLink="false">https://medium.com/p/635a9b46029f</guid>
            <category><![CDATA[kafka]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[message-queue]]></category>
            <dc:creator><![CDATA[Adarsha Jha]]></dc:creator>
            <pubDate>Mon, 01 Sep 2025 00:46:28 GMT</pubDate>
            <atom:updated>2025-09-01T00:46:28.713Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[MinIO in Kubernetes: What It Is and When to Use It]]></title>
            <link>https://medium.com/@adarshajha14/minio-in-kubernetes-what-it-is-and-when-to-use-it-9e0a06ddf3aa?source=rss-69243003cf04------2</link>
            <guid isPermaLink="false">https://medium.com/p/9e0a06ddf3aa</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[kubernetes-cluster]]></category>
            <category><![CDATA[minio]]></category>
            <category><![CDATA[orchestration]]></category>
            <dc:creator><![CDATA[Adarsha Jha]]></dc:creator>
            <pubDate>Mon, 14 Jul 2025 13:03:33 GMT</pubDate>
            <atom:updated>2025-07-14T13:03:33.745Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>MinIO</strong> is a high-performance, S3-compatible object storage solution built for cloud-native environments. It is lightweight, open-source, and designed to run seamlessly in containerized platforms like Kubernetes. Whether you’re storing application backups, machine learning models, or unstructured data such as images and logs, MinIO provides a scalable and efficient way to handle object storage.</p><h3>Deploying MinIO in Kubernetes</h3><p>MinIO is commonly deployed in Kubernetes using the <strong>official Helm chart</strong>, which simplifies configuration, scaling, and integration. The chart enables features like:</p><ul><li><strong>Multi-tenant setup</strong></li><li><strong>TLS/HTTPS encryption</strong></li><li><strong>Persistent storage using PVCs</strong></li><li><strong>Readiness/Liveness probes</strong></li><li><strong>Erasure coding for high availability</strong></li></ul><p>A minimal Helm install command looks like:</p><pre>helm repo add minio https://charts.min.io/<br>helm install my-minio minio/minio --set accessKey=minio,secretKey=minio123</pre><h3>When to Use MinIO in Kubernetes</h3><p>You should consider using MinIO when:</p><ol><li><strong>You Need S3-Compatible Storage in a Private or Hybrid Cloud</strong><br> MinIO acts as a drop-in replacement for AWS S3, enabling you to keep data on-prem while using S3 APIs.</li><li><strong>You Want Fast and Local Object Storage</strong><br> MinIO is optimized for speed, ideal for storing large files and datasets close to your compute resources.</li><li><strong>You Require Cost-Effective Storage</strong><br> MinIO allows full control over infrastructure costs, especially when using your own Kubernetes cluster.</li><li><strong>You Need Object Storage for Cloud-Native Workloads</strong><br> If your microservices, ML pipelines, or observability tools require object storage (e.g., for backups, logs, or artifacts), MinIO is a great fit.</li><li><strong>You’re Building an Air-Gapped or Regulatory-Compliant System</strong><br> When data sovereignty, privacy, or air-gap environments prevent using public cloud storage, MinIO provides a secure alternative.</li></ol><h3>When Not to Use MinIO</h3><ul><li>If you’re already using AWS S3 or GCS and don’t need local object storage.</li><li>If you only need block or file storage (e.g., for databases), not object storage.</li><li>If your Kubernetes cluster has limited resources (MinIO performs best with dedicated volumes and CPU/memory).</li></ul><h3>Conclusion</h3><p>MinIO brings scalable, S3-compatible object storage to Kubernetes with minimal overhead. It is a great choice for teams needing high-performance, cloud-native storage in private, hybrid, or edge environments. By deploying MinIO in your Kubernetes cluster, you gain fast access to storage while keeping full control over your data.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9e0a06ddf3aa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Beginner Level]]></title>
            <link>https://medium.com/@adarshajha14/beginner-level-50fa3cb6ab18?source=rss-69243003cf04------2</link>
            <guid isPermaLink="false">https://medium.com/p/50fa3cb6ab18</guid>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[microservicesarchitecture]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[helm]]></category>
            <dc:creator><![CDATA[Adarsha Jha]]></dc:creator>
            <pubDate>Wed, 25 Jun 2025 08:35:51 GMT</pubDate>
            <atom:updated>2025-06-25T08:35:51.498Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>What are microservices?</strong><br>Microservices is an architectural style where applications are composed of small, loosely coupled services that communicate over HTTP or messaging queues. Each service is independently deployable and focuses on a single business capability.</p><p><strong>Difference from monolithic architecture?</strong><br>Monoliths are a single codebase and deployment unit. Microservices break this into independent services, improving scalability, maintainability, and resilience.</p><p><strong>What is service discovery?</strong><br>It’s the process of automatically detecting network locations of service instances. Tools like Eureka, Consul, or Kubernetes DNS handle this.</p><p><strong>How do microservices communicate?</strong><br>Through REST APIs, gRPC, messaging queues (RabbitMQ, Kafka), or event buses.</p><p><strong>What is an API Gateway?</strong><br>It’s a single entry point for all client requests, handling routing, rate limiting, security, and aggregation (e.g., Kong, NGINX, Istio).</p><p><strong>Common tools?</strong><br>Spring Boot, Docker, Kubernetes, Consul, RabbitMQ, Kafka, Prometheus, Jaeger, Istio.</p><p><strong>What is circuit breaker pattern?</strong><br>It stops calls to a failing service temporarily, preventing cascading failures (e.g., Hystrix, Resilience4j).</p><p><strong>Versioning microservices?</strong><br>Use URI versioning (/v1/api), request header versioning, or deploy new instances with versioned endpoints.</p><p><strong>Config servers?</strong><br>Centralize configuration management (e.g., Spring Cloud Config Server, Consul).</p><p><strong>Synchronous vs Asynchronous communication?</strong><br>Synchronous: Client waits for response (REST, gRPC). Asynchronous: Event/message-based (Kafka, RabbitMQ).</p><h4>Intermediate Level</h4><p><strong>Handling distributed transactions?</strong><br>Use Saga pattern (orchestration/choreography), 2PC (not recommended in microservices), or event-based eventual consistency.</p><p><strong>What are idempotent APIs?</strong><br>APIs that can be called multiple times without changing the result beyond the first call (e.g., PUT /user/123).</p><p><strong>Logging and monitoring?</strong><br>Use centralized logging (ELK, EFK), distributed tracing (Jaeger, Zipkin), and metrics (Prometheus, Grafana).</p><p><strong>Securing communication?</strong><br>Use HTTPS/TLS, mutual TLS (mTLS), OAuth2, JWT, API Gateway policies, and service mesh (Istio).</p><p><strong>Ensuring data consistency?</strong><br>Use event sourcing, distributed locks, or eventual consistency with message queues.</p><p><strong>What is a service mesh?</strong><br>An infrastructure layer for service-to-service communication, with built-in observability, traffic control, and security (e.g., Istio, Linkerd).</p><p><strong>Explain Saga Pattern.</strong><br>A sequence of local transactions where each step publishes an event for the next. Compensation actions are triggered if something fails.</p><p><strong>What is eventual consistency?</strong><br>Data may not be immediately consistent across systems but will be over time. Ensures availability in distributed systems.</p><p><strong>How to scale microservices independently?</strong><br>Deploy each service in containers or separate clusters. Use Kubernetes HPA or separate pipelines per service.</p><p><strong>Testing microservices?</strong></p><ul><li>Unit Testing (JUnit, pytest)</li><li>Integration Testing (with test containers, mocks)</li><li>Contract Testing (Pact)</li><li>End-to-End Testing</li></ul><h4>Advanced Level</h4><p><strong>Schema evolution?</strong><br>Use backward-compatible schema changes, versioned APIs, Avro/Protobuf for event schemas, and schema registry.</p><p><strong>Rate limiting?</strong><br>Implement at API Gateway or service mesh layer using tokens or leaky bucket algorithms.</p><p><strong>Sidecar pattern?</strong><br>Run supporting components (e.g., logging, proxy, security) as sidecars in the same Pod as your app.</p><p><strong>Migrating to microservices?</strong><br>Strangle the monolith: gradually extract services around bounded contexts. Start with least dependent modules.</p><p><strong>Domain-Driven Design (DDD)?</strong><br>Focus on modeling the business domain using bounded contexts and aggregates. Each microservice owns its domain model.</p><p><strong>Debugging distributed systems?</strong><br>Use tracing (Jaeger, OpenTelemetry), centralized logging, and correlation IDs.</p><p><strong>Challenges at scale?</strong></p><ul><li>Service discovery</li><li>Distributed tracing</li><li>Configuration management</li><li>Fault tolerance</li><li>Data consistency</li></ul><p><strong>CI/CD for microservices?</strong><br>Use GitOps, pipelines per service, automated testing, versioned deployments (Helm/Kustomize).</p><p><strong>OAuth2/JWT in microservices?</strong><br>Clients authenticate via OAuth2. JWTs are passed with requests and verified by services or via sidecar/API Gateway.</p><p><strong>Multi-tenant microservices?</strong></p><ul><li>Separate DB per tenant (strong isolation)</li><li>Shared DB with tenant IDs (cost-efficient)</li><li>Namespace or cluster isolation (Kubernetes)</li></ul><h3>☸️ Kubernetes Interview Questions &amp; Answers</h3><h4>Beginner Level</h4><p><strong>What is Kubernetes?</strong><br>An open-source container orchestration platform for automating deployment, scaling, and management of applications.</p><p><strong>What are Pods, Nodes, and Clusters?</strong></p><ul><li>Pod: Smallest deployable unit (1+ containers)</li><li>Node: VM or physical server in cluster</li><li>Cluster: Group of nodes</li></ul><p><strong>Deployment vs ReplicaSet vs StatefulSet?</strong></p><ul><li>Deployment: Declarative updates</li><li>ReplicaSet: Manages replica count (used by Deployments)</li><li>StatefulSet: Maintains identity and order (e.g., for DBs)</li></ul><p><strong>Exposing applications?</strong><br>Via Service objects — ClusterIP, NodePort, LoadBalancer, or Ingress.</p><p><strong>What is a Service?</strong><br>Abstracts access to a set of Pods. Types: ClusterIP (internal), NodePort (external via node IP), LoadBalancer, ExternalName.</p><p><strong>kubectl usage?</strong><br>CLI to interact with Kubernetes. Examples:</p><pre>kubectl get pods<br>kubectl apply -f deployment.yaml</pre><p><strong>ConfigMap vs Secret?</strong><br>Both store configuration, but Secret is base64-encoded and meant for sensitive data (passwords, tokens).</p><p><strong>What is a Namespace?</strong><br>Logical partitioning of cluster resources, useful for multi-tenancy.</p><p><strong>Load balancing in Kubernetes?</strong><br>Handled by Services and kube-proxy or Ingress controllers.</p><p><strong>Rolling update vs Recreate?</strong></p><ul><li>Rolling update: Zero downtime update</li><li>Recreate: Stops all pods, then starts new ones</li></ul><h4>🟡 Intermediate Level</h4><p><strong>What is Helm?</strong><br>A package manager for Kubernetes. Helm charts define, install, and upgrade applications.</p><p><strong>HPA and VPA?</strong></p><ul><li>HPA: Auto-scales pods based on CPU/memory</li><li>VPA: Auto-adjusts resource requests/limits</li></ul><p><strong>etcd?</strong><br>A distributed key-value store used by Kubernetes to store all cluster data/state.</p><p><strong>DaemonSet?</strong><br>Ensures a pod runs on every (or selected) node (e.g., for log collectors).</p><p><strong>Health checks?</strong></p><ul><li>Liveness Probe: Restart container if it fails</li><li>Readiness Probe: Remove pod from Service if not ready</li></ul><p><strong>Init Containers?</strong><br>Run before the main container starts. Used for setup tasks.</p><p><strong>Taints and Tolerations?</strong><br>Control which pods can be scheduled on which nodes.</p><p><strong>Node/Pod affinity?</strong><br>Rules to influence pod scheduling based on labels.</p><p><strong>PersistentVolume vs PersistentVolumeClaim?</strong></p><ul><li>PV: Cluster-wide volume abstraction</li><li>PVC: Request for storage by a pod</li></ul><p><strong>Managing secrets securely?</strong><br>Use Secret objects + RBAC, encrypt secrets at rest, and mount as environment variables or files.</p><h4>🔴 Advanced Level</h4><p><strong>Securing a cluster?</strong></p><ul><li>Use RBAC</li><li>Enable Network Policies</li><li>Use TLS everywhere</li><li>Isolate workloads by namespaces</li><li>Enable PodSecurityPolicies or OPA/Gatekeeper</li></ul><p><strong>Control plane components?</strong></p><ul><li>kube-apiserver</li><li>etcd</li><li>kube-scheduler</li><li>controller-manager</li><li>cloud-controller-manager (optional)</li></ul><p><strong>Custom Resource Definitions (CRDs)?</strong><br>Extend Kubernetes by defining your own resources (e.g., KafkaTopic, BackupJob).</p><p><strong>Troubleshooting pods?</strong></p><ul><li>kubectl describe pod</li><li>kubectl logs</li><li>kubectl get events</li><li>Check container exit codes</li></ul><p><strong>Multi-tenant Kubernetes?</strong><br>Use namespaces, resource quotas, network policies, and optionally separate clusters.</p><p><strong>Service mesh setup?</strong><br>Install Istio/Linkerd via Helm or Operator. Configure sidecars, policies, and observability tools.</p><p><strong>Observability in Kubernetes?</strong></p><ul><li>Logs: Fluent Bit, Loki</li><li>Metrics: Prometheus, Grafana</li><li>Tracing: Jaeger, OpenTelemetry</li></ul><p><strong>Kubernetes upgrade with zero downtime?</strong><br>Use rolling updates, drain and cordon nodes, and stagger upgrades.</p><p><strong>Helm vs Kustomize?</strong></p><ul><li>Helm: Templating engine + packaging</li><li>Kustomize: Pure YAML overlays without templates</li></ul><p><strong>GitOps?</strong><br>Manage infra/config via Git repos. Tools: ArgoCD, Flux. Changes are pulled and applied automatically from Git.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=50fa3cb6ab18" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Concept of choosing Microservices]]></title>
            <link>https://medium.com/@adarshajha14/the-concept-of-choosing-microservices-0db698ac96b9?source=rss-69243003cf04------2</link>
            <guid isPermaLink="false">https://medium.com/p/0db698ac96b9</guid>
            <category><![CDATA[microservice-architecture]]></category>
            <category><![CDATA[microservices-pattern]]></category>
            <category><![CDATA[microservices]]></category>
            <dc:creator><![CDATA[Adarsha Jha]]></dc:creator>
            <pubDate>Tue, 01 Apr 2025 07:48:13 GMT</pubDate>
            <atom:updated>2025-04-01T07:48:13.236Z</atom:updated>
            <content:encoded><![CDATA[<p>In <strong>Service-Oriented Architecture (SOA)</strong>, software is broken into small, interconnected business units that communicate using various protocols. <strong>Microservices Architecture (MSA)</strong> takes this further — it’s an implementation approach to SOA, where services are even more independent and lightweight.</p><h3>Key Principles of Microservices</h3><ol><li><strong>Independence</strong> — Each microservice should be independently deployable.</li><li><strong>Loose Coupling</strong> — Changes in one service shouldn’t affect others.</li><li><strong>Focused Business Goal</strong> — Each microservice should serve a single, well-defined purpose.</li></ol><h3>Microservices Design Patterns</h3><p>To tackle challenges in MSA, design patterns help structure and optimize services:</p><ul><li><strong>Decomposition Patterns</strong> — Breaking an application into logically independent microservices.</li><li><strong>Integration Patterns</strong> — Handling communication and combining multiple service responses.</li><li><strong>Database Patterns</strong> — Structuring databases (e.g., separate DB per service vs. shared DB).</li><li><strong>Observability Patterns</strong> — Ensuring logging, monitoring, and performance tracking.</li><li><strong>Cross-Cutting Concerns</strong> — Managing service discovery, external configurations, and deployments.</li></ul><p>By following these principles and patterns, microservices stay scalable, resilient, and easy to manage.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0db698ac96b9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding Container Runtimes in Kubernetes]]></title>
            <link>https://medium.com/@adarshajha14/understanding-container-runtimes-in-kubernetes-7d257b6b3d91?source=rss-69243003cf04------2</link>
            <guid isPermaLink="false">https://medium.com/p/7d257b6b3d91</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[kubernetes-cluster]]></category>
            <category><![CDATA[containerd]]></category>
            <category><![CDATA[kubeadm]]></category>
            <category><![CDATA[kubernetes-engine]]></category>
            <dc:creator><![CDATA[Adarsha Jha]]></dc:creator>
            <pubDate>Thu, 06 Mar 2025 12:34:18 GMT</pubDate>
            <atom:updated>2025-03-06T12:34:18.666Z</atom:updated>
            <content:encoded><![CDATA[<h3>Q1: What is a container runtime in Kubernetes?</h3><p><strong>A:</strong> A container runtime is software that runs containers and is responsible for managing their lifecycle, including starting, stopping, and removing containers. Kubernetes relies on a container runtime to run containerized workloads.</p><h3>Q2: What are the key container runtimes supported by Kubernetes?</h3><p><strong>A:</strong> Kubernetes supports multiple container runtimes, including:</p><ul><li><strong>containerd</strong> — A lightweight and widely used container runtime.</li><li><strong>CRI-O</strong> — An optimized runtime designed specifically for Kubernetes.</li><li><strong>Docker Engine (through </strong><strong>dockershim in earlier versions)</strong> – Deprecated in newer Kubernetes versions.</li><li><strong>Other CRI-compliant runtimes</strong> — Any runtime that implements the <a href="https://chatgpt.com/?q=Container%20Runtime%20Interface%20(CRI)">Container Runtime Interface (CRI)</a>.</li></ul><h3>Q3: What is the Container Runtime Interface (CRI)?</h3><p><strong>A:</strong> The <a href="https://chatgpt.com/?q=Container%20Runtime%20Interface%20(CRI)">Container Runtime Interface (CRI)</a> is an API that allows Kubernetes to communicate with different container runtimes. It standardizes the way Kubernetes interacts with container runtimes, enabling flexibility in runtime selection.</p><h3>Q4: Why was dockershim deprecated in Kubernetes?</h3><p><strong>A:</strong> The dockershim component was deprecated because Kubernetes shifted towards using CRI-compliant runtimes like containerd and CRI-O, which offer better integration, lower resource overhead, and direct compatibility with Kubernetes features.</p><h3>Q5: How do you check which container runtime is being used on a Kubernetes node?</h3><p><strong>A:</strong> You can check the runtime using the following command:</p><blockquote>kubectl get nodes -o wide</blockquote><blockquote>Or, for a more detailed runtime check:</blockquote><blockquote>crictl info</blockquote><blockquote>(Ensure crictl is installed for this command to work.)</blockquote><h3>Q6: What are the benefits of using containerd as a runtime for Kubernetes?</h3><p><strong>A:</strong> containerd is preferred due to:</p><ul><li><strong>Native CRI support</strong> — Directly integrates with Kubernetes.</li><li><strong>Lightweight design</strong> — Focuses solely on container execution without extra features.</li><li><strong>Better performance</strong> — Lower resource usage compared to full Docker Engine.</li></ul><h3>Q7: How do you install containerd on a Kubernetes node?</h3><p><strong>A:</strong> The steps include:</p><ol><li>Install necessary dependencies:</li></ol><p>sudo apt update &amp;&amp; sudo apt install -y containerd</p><p>sudo systemctl restart containerd</p><p>crictl info</p><h3>Q9: How do you switch container runtimes in Kubernetes?</h3><p><strong>A:</strong> To switch container runtimes:</p><ol><li><strong>Stop the existing runtime</strong> (e.g., systemctl stop docker).</li><li><strong>Install and configure the new runtime</strong> (e.g., containerd or CRI-O).</li><li><strong>Modify the kubelet configuration file (</strong><strong>/var/lib/kubelet/kubeadm-flags.env)</strong> to point to the new runtime.</li><li><strong>Restart the kubelet</strong> using systemctl restart kubelet.</li></ol><h3>Q10: What should you consider when choosing a container runtime for production Kubernetes clusters?</h3><p><strong>A:</strong> Considerations include:</p><ul><li><strong>Kubernetes compatibility</strong> — Ensure the runtime is CRI-compliant.</li><li><strong>Performance &amp; resource usage</strong> — Lighter runtimes like containerd and CRI-O improve efficiency.</li><li><strong>Security</strong> — Use a runtime with strong security measures and frequent updates.</li><li><strong>Support &amp; ecosystem</strong> — Choose a well-supported runtime with an active community.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7d257b6b3d91" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating a Custom Fabric Network: A New Platform for Blockchain Customization]]></title>
            <link>https://medium.com/@adarshajha14/creating-a-custom-fabric-network-a-new-platform-for-blockchain-customization-52b97698edb7?source=rss-69243003cf04------2</link>
            <guid isPermaLink="false">https://medium.com/p/52b97698edb7</guid>
            <category><![CDATA[hyperledger]]></category>
            <category><![CDATA[hyperledger-fabric]]></category>
            <dc:creator><![CDATA[Adarsha Jha]]></dc:creator>
            <pubDate>Sun, 24 Nov 2024 18:10:10 GMT</pubDate>
            <atom:updated>2024-11-25T04:20:53.959Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Creating a Custom Fabric Network: A New Platform for Blockchain Customization</strong></p><p>In the ever-evolving world of blockchain technology, flexibility and customization have become essential. One of the most powerful platforms available today for businesses and developers is Hyperledger Fabric, a modular blockchain framework that allows for the development of custom blockchain networks. However, configuring and managing these networks often presents challenges, especially when it comes to scaling or tailoring them to unique business needs.</p><p>To address these challenges, my friend Pawan Adhav created a new platform, Custom Fabric, designed to streamline and simplify the process of creating any custom Hyperledger Fabric network. This platform allows users to configure an unlimited number of orgs, channels, and peers, empowering businesses to build a blockchain network that fits their specific requirements.<br>Key Features of the Custom Fabric Platform</p><p>Customizable Network Configuration: With the Custom Fabric platform, users can easily configure any number of organizations (orgs), channels, and peers. Whether you are building a small network for internal use or scaling up for a large enterprise solution, the platform’s flexibility ensures that your blockchain network can grow and adapt as needed.<br> Organizations (Orgs): You can define and customize multiple organizations within your network. Each organization will have its own set of peers and policies, ensuring security and access control that align with your specific requirements.<br> Channels: The platform enables the configuration of multiple channels, allowing for secure, private communication between different groups of participants in your network.<br> Peers: You can add and configure any number of peers to handle transactions and maintain the ledger for each organization in your network.</p><p>Automatic Folder Structure Generation: Building a blockchain network from scratch involves a variety of configurations, files, and dependencies. Custom Fabric takes care of this by automatically generating a well-organized folder structure for your network setup. This folder structure includes all the essential components needed to deploy and run your blockchain network, including:<br> Blockchain Network Setup: The platform creates the necessary files to set up your Fabric network, such as configuration files, certificates, and keys.<br> API: The platform auto-generates API endpoints that allow seamless communication between your blockchain network and external applications. This helps you quickly integrate your network with front-end applications or third-party services.<br> Caliper: Performance benchmarking is a crucial aspect of any blockchain network. Custom Fabric automatically generates Caliper configuration files for benchmarking the performance of your network. You can run tests to understand throughput, transaction latency, and other key metrics.<br> Explorer: The platform also sets up a Fabric Explorer, a UI tool that helps you visualize the data on your blockchain network. You can monitor blocks, transactions, channels, and peers, all in real-time.</p><p>Scalability and Flexibility: One of the biggest advantages of Custom Fabric is its ability to scale and adapt. Whether you’re experimenting with a prototype or deploying a production-grade network, the platform’s architecture allows you to scale your network up or down, add new orgs or channels as necessary, and experiment with different configurations — all without manually tweaking complex configurations or worrying about system limitations.</p><p>User-Friendly Interface: The platform features a clean, user-friendly interface that allows developers and administrators to quickly navigate the setup process. You can simply input your desired network configurations, and the platform will automatically generate all the required files and structures for you. This dramatically reduces setup time and eliminates common configuration errors.</p><p>How to Get Started</p><p>Getting started with Custom Fabric is simple. Head over to the platform at <a href="https://custom-fabric.bytehash.tech/">https://custom-fabric.bytehash.tech/</a>, where you can access a straightforward dashboard to create your customized Hyperledger Fabric network.</p><p>Here’s how it works:</p><p>Create a New Network: Begin by entering the parameters for your custom blockchain network. Specify the number of organizations, channels, and peers you wish to configure.<br> Download the Configuration: Once you’ve finalized your setup, download the folder structure and all configuration files.<br> Deploy and Manage Your Network: Use the generated files to deploy your network. You’ll also have access to the API and Caliper configurations for performance testing and integration.</p><p>Why Choose Custom Fabric?</p><p>Creating a custom blockchain network often requires expertise in Hyperledger Fabric’s various components and configuration options. Custom Fabric simplifies this process, offering a powerful yet easy-to-use platform for developers and organizations alike.</p><p>By automating much of the setup and providing a clear folder structure, the platform reduces setup time, minimizes errors, and accelerates your development cycle. Whether you’re testing out new ideas or building a production-ready blockchain network, Custom Fabric provides the tools necessary for creating a robust, scalable, and secure blockchain infrastructure.</p><p>If you want to streamline your Hyperledger Fabric network creation process, visit <a href="https://custom-fabric.bytehash.tech/">https://custom-fabric.bytehash.tech/</a> and start building your custom blockchain network today!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=52b97698edb7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Create a CICD pipeline in gitlab]]></title>
            <link>https://medium.com/@adarshajha14/create-a-cicd-pipeline-in-gitlab-e3b59536ffe3?source=rss-69243003cf04------2</link>
            <guid isPermaLink="false">https://medium.com/p/e3b59536ffe3</guid>
            <category><![CDATA[cicd-pipeline]]></category>
            <category><![CDATA[yaml]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[gitlab]]></category>
            <category><![CDATA[cicd]]></category>
            <dc:creator><![CDATA[Adarsha Jha]]></dc:creator>
            <pubDate>Wed, 27 Dec 2023 07:58:48 GMT</pubDate>
            <atom:updated>2023-12-27T07:58:48.156Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Create a CICD pipeline in gitlab</strong></p><p>Setting up a CI/CD pipeline using GitLab involves creating a .gitlab-ci.yml file to define your pipeline stages and jobs. Here&#39;s a step-by-step guide:</p><h3>Step 1: Set Up Your GitLab Repository</h3><ol><li><strong>Create a new GitLab repository:</strong></li></ol><ul><li>Go to your GitLab account and create a new project.</li></ul><p><strong>2. Clone the repository:</strong></p><ul><li>Clone the repository to your local machine using Git.</li></ul><h3>Step 2: Create a Simple Web Application</h3><p>Create a simple web application in the same way as described in the GitHub example.</p><h3>Step 3: Define .gitlab-ci.yml</h3><ol><li><strong>Create a </strong><strong>.gitlab-ci.yml file:</strong></li></ol><ul><li>In the root of your GitLab repository, create a file named .gitlab-ci.yml.</li></ul><ol><li><strong>Define your CI/CD pipeline:</strong></li></ol><ul><li>Use the following template as a starting point for your pipeline:</li></ul><pre>stages:<br> - build<br> - test<br> - deploy<br>variables:<br> HEROKU_APP_NAME: &quot;your-heroku-app-name&quot;<br>before_script:<br> - apt-get update -qy<br> - apt-get install -y nodejs npm<br>build:<br> stage: build<br> script:<br> - npm install<br>test:<br> stage: test<br> script:<br> - npm test<br>deploy:<br> stage: deploy<br> script:<br> - apt-get install -y ruby-dev<br> - gem install dpl<br> - dpl - provider=heroku - app=$HEROKU_APP_NAME - api-key=$HEROKU_API_KEY<br> only:<br> - main</pre><p>Replace &quot;your-heroku-app-name&quot; with the actual name of your Heroku app.</p><ol><li><strong>Configure CI/CD Variables:</strong></li></ol><ul><li>Go to your GitLab repository &gt; Settings &gt; CI/CD &gt; Variables.</li><li>Add a new variable named HEROKU_API_KEY with your Heroku API key.</li></ul><h3>Step 4: Test the CI/CD Pipeline</h3><ol><li><strong>Push changes to GitLab:</strong></li></ol><ul><li>Commit and push your changes to the GitLab repository.</li></ul><p><strong>2. Check the pipeline status:</strong></p><ul><li>Go to your GitLab repository &gt; CI/CD &gt; Pipelines to monitor the progress and status of the pipeline.</li></ul><p><strong>3. Verify deployment:</strong></p><ul><li>Once the pipeline completes successfully, check your Heroku app to ensure it has been deployed.</li></ul><p>Congratulations! You’ve set up a basic CI/CD pipeline using GitLab CI/CD and deployed a simple web application. Adjust the pipeline configuration based on your project’s specific needs.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e3b59536ffe3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Certificate rotation in Hyperledger fabric 1.4.x]]></title>
            <link>https://medium.com/@adarshajha14/certificate-rotation-in-hyperledger-fabric-1-4-x-bd09a89591c5?source=rss-69243003cf04------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd09a89591c5</guid>
            <category><![CDATA[hyperledger-fabric]]></category>
            <category><![CDATA[certificate-expiration]]></category>
            <category><![CDATA[hyperledger-fabric-ca]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[hyperledger]]></category>
            <dc:creator><![CDATA[Adarsha Jha]]></dc:creator>
            <pubDate>Thu, 05 Aug 2021 06:50:26 GMT</pubDate>
            <atom:updated>2021-08-05T07:35:18.759Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Certificate rotation in Hyperledger fabric 1.4.x version </strong>when certificates of peer and ordererer nodes expires ?</p><p>Create new admin and enrollment certs for all orderers<br>2. Upgraded peer, orderer and cli binaries to 1.4.9 from 1.4.2 or any other version. ( You can do this by simply downloading the latest binaries and adding them in your yaml files )<br>3. Added these two environment variables in all the orderers:<br><strong>`- ORDERER_GENERAL_TLS_TLSHANDSHAKETIMESHIFT=1240h </strong>( this shifts back the time of certificates to 1240h , so we have to add according to when our certificates expired ) and the other variable is :-<br>-<strong>ORDERER_GENERAL_AUTHENTICATION_NOEXPIRATIONCHECKS=true`<br></strong>4. Spin up all the orderers and they start raft consensus between them<br>5. Fetch config and modify config from the bootstrapped orderer CLI<br>6. Move old certs in orderer organization<br>7. Reverse the time in the server by using the below commands in your terminal<br>`<strong>sudo timedatectl set-ntp no</strong><br><strong>sudo timedatectl set-time 2020–12–15<br>timedatectl`<br></strong>8. Sign the config from the orderer organization<br>9. Reset the time of the server<br><strong>`sudo timedatectl set-ntp yes<br>sudo hwclock — systohc — localtime`</strong><br>10. Move new certs in orderer server<br>11. Generate new tls certs for all orderers(in a new directory)<br>12. Update the config with new admin cert for Orderer MSP and new TLS cert for one of the orderer in the consenter section in all the 4 channels(1 system and 3 application channel)<br>13. Fetch the latest config block from the system channel<br>14. Add new tls certs for this orderer in the orderer organization directory and passed new config block</p><p>ORDERER_GENERAL_GENESISFILE=/var/hyperledger/orderer/orderer.newgenesis.block`<br> 15. Restart the updated orderer</p><p># The most important point is if in case you have more than two orderers in your network then try to remove all the orderers and leave your network with just two orderers and then follow the procedure from point 1 to point 15.</p><blockquote>It took me almost 15 days to solve this bug when happened to me. I solved it with my friend <a href="https://www.linkedin.com/in/trinayan-bhatt-10370b145/">Trinayan Bhatt </a>Who helped me religiously to solve this bug and of course the maintainers of fabric also helped me by answering me on JIRA regularly . I know this a bug which would have screwed your happiness till now but don’t worry just follow this article carefully and you will be able to restart your stopped network with new peer and orderer certs.</blockquote><p>I hope this article helped you and if yes please follow me on medium for more interesting articles and also follow me on <a href="https://www.instagram.com/jhaadarsha/?hl=en">instagram</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd09a89591c5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>