Raj S retweeted
How does Git work? To begin with, it's essential to identify where our code is stored.
Credit to @bytebytego
#cybersecurity #cybersecurityawareness #infosec #SOC #Networks #cheatsheet
Raj S retweeted
๐๐ผ๐ป๐๐ฎ๐ถ๐ป๐ฒ๐ฟ๐ ๐๐ ๐ฉ๐ถ๐ฟ๐๐๐ฎ๐น ๐ ๐ฎ๐ฐ๐ต๐ถ๐ป๐ฒ๐ ๐๐ ๐ฆ๐ฎ๐ป๐ฑ๐ฏ๐ผ๐
๐ฒ๐.
Do you know the differences?
Containers isolate processes.
VMs isolate operating systems.
Sandboxes restrict what untrusted code can access.
But when the code comes from an AI agent, containing the run is only half of it.
The agent's output still has to land somewhere: the company's codebase, its live product. A sandbox limits what code can touch while it runs, not what ships afterwards.
So the boundary has two parts: an isolated place for the agent to work, and a review step before changes reach production.
Replit runs agents in isolated cloud environments, away from employee laptops. For work on an existing company codebase, agents turn their work into proposed changes for engineering to review.
The agent proposes the change.
Engineering decides what ships.
๐ฆ๐ฒ๐ฒ ๐ต๐ผ๐ ๐ฅ๐ฒ๐ฝ๐น๐ถ๐ ๐ฟ๐๐ป๐ ๐ฎ๐ด๐ฒ๐ป๐๐ ๐ณ๐ผ๐ฟ ๐ฐ๐ผ๐บ๐ฝ๐ฎ๐ป๐ถ๐ฒ๐ โ lucode.co/replit-for-businesโฆ
Read the post below for more details on ๐๐ผ๐ป๐๐ฎ๐ถ๐ป๐ฒ๐ฟ๐ ๐๐ ๐ฉ๐ถ๐ฟ๐๐๐ฎ๐น ๐ ๐ฎ๐ฐ๐ต๐ถ๐ป๐ฒ๐ ๐๐ ๐ฆ๐ฎ๐ป๐ฑ๐ฏ๐ผ๐
๐ฒ๐.
Thanks to @Replit for sponsoring this post.
๐๐ผ๐ป๐๐ฎ๐ถ๐ป๐ฒ๐ฟ๐ ๐๐ ๐ฉ๐ถ๐ฟ๐๐๐ฎ๐น ๐ ๐ฎ๐ฐ๐ต๐ถ๐ป๐ฒ๐ ๐๐ ๐ฆ๐ฎ๐ป๐ฑ๐ฏ๐ผ๐
๐ฒ๐.
Do you know the differences?
A ๐ฐ๐ผ๐ป๐๐ฎ๐ถ๐ป๐ฒ๐ฟ isolates processes on a shared kernel. Namespaces control what each process can see, and cgroups control what resources it can use. They start fast and pack densely on one host.
For stronger isolation, ๐๐ถ๐ฟ๐๐๐ฎ๐น ๐บ๐ฎ๐ฐ๐ต๐ถ๐ป๐ฒ๐ run their own operating systems. A hypervisor gives each VM virtual hardware and a separate guest kernel, creating a stronger boundary between workloads.
When the code itself canโt be trusted, thatโs where ๐๐ฎ๐ป๐ฑ๐ฏ๐ผ๐
๐ถ๐ป๐ด comes in. Sandboxes restrict what code can access, such as system calls, network connections, and files. Often built on containers or lightweight VMs, they can use technologies like gVisor, Firecracker, or seccomp filters.
Containers isolate processes. VMs isolate operating systems. Sandboxes restrict what untrusted code can access.
But when the code comes from an AI agent, containing the run is only half of it.
The agent's output still has to land somewhere: the company's codebase, its live product. A sandbox limits what code can touch while it runs, not what ships afterwards.
So the boundary has two parts: an isolated place for the agent to work, and a review step before changes reach production. Replit runs agents in isolated cloud environments, away from employee laptops. For work on an existing company codebase, agents turn their work into proposed changes for engineering to review.
The agent proposes the change. Engineering decides what ships.
๐ฆ๐ฒ๐ฒ ๐ต๐ผ๐ ๐ฅ๐ฒ๐ฝ๐น๐ถ๐ ๐ฟ๐๐ป๐ ๐ฎ๐ด๐ฒ๐ป๐๐ ๐ณ๐ผ๐ฟ ๐ฐ๐ผ๐บ๐ฝ๐ฎ๐ป๐ถ๐ฒ๐ โ lucode.co/replit-for-businesโฆ
What else would you add?
โโ
โป๏ธ Repost to help others learn and grow.
๐ Thanks to @Replit for sponsoring this post.
โ Follow me ( Nikki Siapno ) to improve at system design and AI.
Raj S retweeted
Ever wondered how Spring Security handles authentication and authorization? ๐
Spring Security Filter Chain!
Every HTTP request passes through a chain of security filters before reaching your controller.
Hereโs how it works:
๐ฅ Request enters the filter chain
๐ Authentication filter checks credentials
๐ก๏ธ Authorization filter checks permissions
โ
Authorized request reaches the controller
โ Unauthorized request gets rejected
Why use it?
โ
Centralized security
โ
JWT and OAuth2 support
โ
Role-based access control
โ
Custom security filters
A must-know concept for Java backend developers!
#Java #SpringBoot #SpringSecurity #BackendDevelopment
๐ค Made with AI
Raj S retweeted
Every time you order food, book a cab, make a payment, or track a deliveryโฆ thousands of events are moving behind the scenes in real time.
Thatโs where Kafka comes in.
Kafka is one of the most important tools in modern data engineering because it helps systems move, process, and react to data instantly.
But to understand Kafka properly, you first need to understand its core building blocks:
Producer: Sends events into Kafka continuously.
Topic: Organizes related events into named streams.
Partition: Splits topic data for parallel processing.
Consumer: Reads and processes events from topics.
Consumer Group: Helps multiple consumers share the workload.
Broker: Stores and serves Kafka topic data.
Cluster: Connects multiple brokers for scale and resilience.
Offset: Tracks the exact position of each message.
Replication: Copies data across brokers for reliability.
Retention: Keeps messages based on time or size rules.
Schema Registry: Manages event formats between systems.
Kafka Connect: Moves data between Kafka and external tools.
Once these concepts are clear, Kafka becomes much easier to understand.
It is not just a messaging system.
It is the backbone of real-time apps, fraud detection, payments, IoT, analytics, recommendation engines, and modern data pipelines.
Master these 12 concepts, and youโll understand how real-time data actually flows.
P.S. Preparing for a software engineering role? Check out my book, System Design and Behavioral Intelligence.
It will help you:
โขโ โ Build strong System Design foundations and approach design problems with confidence
โขโ โ Develop practical frameworks to navigate complex behavioral and leadership challenges
Get Your Copy anywhere internationally:
US: lnkd.in/eVy2ACxQ
UK: lnkd.in/evzmHKm4
India : lnkd.in/e25PthqU
Raj S retweeted
A beginner's guide to Hibernate SQM (Semantic Query Model)
vladmihalcea.com/hibernate-sโฆ
Raj S retweeted
System Design Fundamentals Tutorial Series (AI Era Edition)
Master System Design from zero to advanced. Learn how modern applications are architected, designed, scaled, secured, and optimized by building real-world systems every day.
30 Days. 30 Topics. 30 Hands-On Projects.
โ Day 1: Introduction to System Design โ What Is System Design? High-Level Design (HLD), Low-Level Design (LLD), and Why System Design Matters.
Project: Design a URL Shortener architecture.
โก Day 2: Client-Server Architecture โ Clients, Servers, Requests, Responses, HTTP, HTTPS, and Communication Protocols.
Project: Build a simple client-server application.
โข Day 3: Monolithic vs Microservices Architecture โ Architecture Patterns, Service Boundaries, Advantages, and Trade-offs.
Project: Design an e-commerce application using both architectures.
โฃ Day 4: Networking Fundamentals โ TCP/IP, DNS, HTTP, HTTPS, WebSockets, Proxies, and Reverse Proxies.
Project: Design a real-time messaging communication system.
โค Day 5: API Design โ REST, GraphQL, gRPC, API Versioning, Rate Limiting, and API Gateways.
Project: Design a scalable API for a social media platform.
โฅ Day 6: Database Fundamentals โ SQL vs NoSQL, Relational Databases, Document Databases, and Data Modeling.
Project: Design a database for an online marketplace.
โฆ Day 7: Database Scaling โ Indexing, Replication, Sharding, Partitioning, and Connection Pooling.
Project: Design a horizontally scalable database architecture.
โง Day 8: Caching Strategies โ Redis, Memcached, Cache-Aside, Write-Through, Write-Back, and Cache Invalidation.
Project: Design a high-performance product caching system.
โจ Day 9: Load Balancing โ L4 vs L7 Load Balancers, Algorithms, Health Checks, and Failover.
Project: Design a load-balanced web application.
โฉ Day 10: Scalability Fundamentals โ Vertical Scaling, Horizontal Scaling, Bottlenecks, and Performance Optimization.
Project: Design a system that supports one million users.
โช Day 11: Distributed Systems Fundamentals โ Distributed Nodes, Communication, Coordination, and Fault Tolerance.
Project: Design a distributed key-value store.
โซ Day 12: CAP Theorem and PACELC โ Consistency, Availability, Partition Tolerance, and Latency Trade-offs.
Project: Design a distributed database architecture.
โฌ Day 13: Consistency Models โ Strong Consistency, Eventual Consistency, Causal Consistency, and Read-After-Write.
Project: Design a globally distributed user profile system.
โญ Day 14: Message Queues and Event-Driven Architecture โ Kafka, RabbitMQ, Amazon SQS, Pub/Sub, and Asynchronous Processing.
Project: Build an event-driven order processing system.
โฎ Day 15: Storage Systems and Object Storage โ Block Storage, File Storage, Object Storage, Amazon S3, and Data Durability.
Project: Design a scalable cloud file storage system.
โฏ Day 16: Reliability and Fault Tolerance โ Redundancy, Failover, Circuit Breakers, Retries, and Disaster Recovery.
Project: Design a highly available payment processing system.
โฐ Day 17: High Availability and Disaster Recovery โ Multi-AZ, Multi-Region, Backups, Replication, RTO, and RPO.
Project: Design a globally available application.
โฑ Day 18: Security in System Design โ Authentication, Authorization, OAuth 2.0, JWT, Encryption, and Zero Trust.
Project: Design a secure authentication service.
โฒ Day 19: Observability and Monitoring โ Logging, Metrics, Distributed Tracing, Prometheus, Grafana, and OpenTelemetry.
Project: Design a complete application monitoring platform.
โณ Day 20: Performance Engineering โ Latency, Throughput, Concurrency, Benchmarking, Profiling, and Optimization.
Project: Optimize a slow API for high traffic.
ใ Day 21: Real-Time System Design โ WebSockets, Server-Sent Events, Long Polling, and Real-Time Data Streaming.
Project: Design a WhatsApp-like messaging system.
ใ Day 22: Containerization and Orchestration โ Docker, Kubernetes, Containers, Service Discovery, and Deployment Strategies.
Project: Design a containerized microservices platform.
ใ Day 23: Cloud-Native System Design โ AWS, Azure, Google Cloud, Serverless Computing, and Infrastructure as Code.
Project: Design a cloud-native SaaS application.
ใ Day 24: CI/CD and Deployment Architecture โ Continuous Integration, Continuous Delivery, Blue-Green Deployment, and Canary Releases.
Project: Design an automated deployment pipeline.
ใ Day 25: System Design for AI Applications โ LLMs, Model Serving, GPU Infrastructure, Inference Pipelines, and AI Workloads.
Project: Design a scalable AI chatbot architecture.
ใ Day 26: RAG System Design โ Embeddings, Vector Databases, Semantic Search, Retrieval Pipelines, and LLM Integration.
Project: Build a production-ready document Q&A system.
ใ Day 27: AI Agent System Design โ Agent Orchestration, Tool Calling, Memory, Planning, MCP, and Multi-Agent Systems.
Project: Design an autonomous AI agent platform.
ใ Day 28: Distributed AI Infrastructure โ Model Scaling, GPU Scheduling, Inference Caching, Model Routing, and Cost Optimization.
Project: Design a scalable LLM inference platform.
ใ Day 29: System Design Interview Preparation โ Requirements Gathering, Capacity Estimation, Architecture Diagrams, Trade-offs, and Design Communication.
Project: Complete a mock system design interview for YouTube.
ใ Day 30: Final Capstone Project โ Design a Production-Ready Global AI SaaS Platform โ Microservices, API Gateway, Load Balancing, Distributed Databases, Redis, Kafka, Kubernetes, RAG, AI Agents, Authentication, Observability, Security, High Availability, and Auto Scaling.
Goal: Become confident in designing scalable, reliable, secure, and production-ready systems.
Grab the System Design Fundamentals Ebook:
codewithdhanian.gumroad.com/โฆ
Follow @e_opore to learn more.
Raj S retweeted
Day 1/30 - System Design Series
Introduction to System Design
What Is System Design?
System Design is the process of defining the architecture, components, modules, interfaces, and data flow of a system to meet specific requirements.
1. High-Level Design (HLD)
โ Defines the overall architecture of a system.
โ Identifies major components and their interactions.
โ Describes how services communicate with each other.
โ Focuses on scalability, availability, reliability, and performance.
โ Includes architecture diagrams, databases, APIs, and infrastructure.
2. Low-Level Design (LLD)
โ Focuses on the internal implementation of individual components.
โ Defines classes, objects, methods, and functions.
โ Describes database schemas and relationships.
โ Covers design patterns and business logic.
โ Focuses on maintainability, code structure, and reusability.
3. Why System Design Matters
โ Helps build scalable applications.
โ Improves system performance.
โ Prevents single points of failure.
โ Ensures high availability and reliability.
โ Makes applications easier to maintain.
โ Helps manage increasing user traffic.
โ Reduces infrastructure costs.
โ Improves security and fault tolerance.
Project: Design a URL Shortener Architecture
Build a system similar to Bitly that converts long URLs into short, shareable links.
What to design:
โ URL shortening API.
โ Unique short code generation.
โ URL redirection service.
โ Database schema for storing URLs.
โ Cache layer using Redis.
โ Analytics and click tracking.
โ Rate limiting and abuse prevention.
โ High availability and scalability.
Source Code:
codepen.io/editor/Code-WithDโฆ
Grab the System Design ebook:
codewithdhanian.gumroad.com/โฆ
Raj S retweeted
WebSockets vs SSE vs Polling โก๐
Three ways to deliver updates to your users, but each works differently.
Here's how they compare ๐
๐ต 1. WebSockets - Two-way communication
โ๏ธ Client and server exchange messages over one persistent connection.
โก Updates arrive instantly with minimal overhead.
๐ฌ Ideal for real-time chat, multiplayer games, and collaboration.
โ ๏ธ Requires connection management and reconnect logic.
๐ 2. Server-Sent Events (SSE) - One-way streaming
โก๏ธ Server continuously pushes updates to connected clients over HTTP.
๐ก Great for live feeds, notifications, and progress updates.
๐ Browser EventSource supports automatic reconnection.
โ ๏ธ Clients must use separate HTTP requests to send data.
๐ต 3. Polling - Periodic requests
๐ Client repeatedly checks the server for new information.
โฑ๏ธ Update freshness depends on the polling interval.
๐ Ideal for status checks and simple dashboards.
โ ๏ธ Repeated requests create overhead, even when nothing changes.
๐ก The main difference:
WebSockets โ Interactive, two-way updates
SSE โ Continuous server-to-client updates
Polling โ Simple, scheduled checks
Choose based on how quickly updates must arrive and how much complexity your application needs. ๐
Raj S retweeted
How to speed up SQL Server using the useBulkCopyForBatchInsert configuration property
vladmihalcea.com/sql-server-โฆ
Raj S retweeted
๐ฆ๐๐ข ๐๐ ๐ฆ๐๐ ๐๐ ๐ฆ๐๐.
An ๐ฆ๐๐ (Service Level Indicator) measures whatโs actually happening in your system; like request latency, error rate, or uptime. Itโs the raw signal that tells you how your service is performing.
An ๐ฆ๐๐ข (Service Level Objective) defines the acceptable range for an SLI, like โ99.9% of requests succeed within 200ms.โ Itโs what your team aims to achieve to maintain reliability.
An ๐ฆ๐๐ (Service Level Agreement) is a formal contract with users or customers, often tied to penalties if targets arenโt met. It defines the consequences, not just the goal.
But a service isn't the only thing teams hold to a target.
A roadmap is a target too: which initiatives get the people, time and budget. Most roadmaps have no SLI behind them. People move, priorities shift, AI agents take on work without status updates, and the gap between plan and reality grows quietly.
Measuring that gap starts with the data work already produces. Tempo Loop connects time, capacity, spend and financials into one continuously updated view of whether the work still matches the strategy that funded it, for human and AI work alike.
๐๐
๐ฝ๐น๐ผ๐ฟ๐ฒ ๐ง๐ฒ๐บ๐ฝ๐ผ ๐๐ผ๐ผ๐ฝ โ lucode.co/tempo-loop-z72xd
What else would you add?
โโ
โป๏ธ Repost to help others learn and grow.
๐ Thanks to @TempoHQ for sponsoring this post.
โ Follow me ( Nikki Siapno ) to improve at AI and system design.
Raj S retweeted
Senior backend interview question:
A nightly job ran fine for 11 months.
Now it runs twice every night.
No deploy.
No config change.
No code change.
What are you checking first?
Raj S retweeted
How to find which statement failed in a JDBC Batch Update
vladmihalcea.com/how-to-findโฆ
Raj S retweeted
Hibernate StatelessSession JDBC Batching
vladmihalcea.com/hibernate-sโฆ
Raj S retweeted
20 API Design strategies for versioning and deprecation.
Grab API Design ebook: codewithdhanian.gumroad.com/โฆ





























