Rishabh

@manoge @0007arsh @PRSundar64 @arivalayam did u check ur bookmark ?

@0007arsh @PRSundar64 @arivalayam Bookmarking this post to see how gobar bakths react.

Betting Market Predictions: Assam: BJP clear winner West Bengal: Close call, TMC has edge. Kerala: Close call, Communist has edge. TN: DMK clear winner.

35 WEBSITES THAT ARE ACTUALLY USEFUL 1. archive. org — access old content 2. wolframalpha. com — solve anything 3. removebg. com — remove image background 4. tinypng. com — compress images free 5. smallpdf. com — edit PDFs free 6. ilovepdf. com — merge & split PDFs 7. deepl. com — best translator online 8. grammarly. com — fix your writing 9. hemingwayapp. com — simplify writing 10. chatgpt. com — ask any question 11. perplexity. ai — smart search engine 12. notion. so — organize your whole life 13. trello. com — manage any project 14. canva. com — design for free 15. unsplash. com — free photos 16. pexels. com — free videos & photos 17. flaticon. com — free icons 18. coolors. co — pick color palettes 19. fonts. google. com — free fonts 20. namecheap. com — buy cheap domains 21. github. com — free code hosting 22. replit. com — code from browser 23. regex101. com — test any code 24. explainshell. com — understand commands 25. fast. com — check internet speed 26. haveibeenpwned. com — check if hacked 27. virustotal. com — scan files for virus 28. downdetector. com — check if site is down 29. 10minutemail. com — temp email address 30. justpaste. it — share text instantly 31. screely. com — make screenshots beautiful 32. carbon. now. sh — share code beautifully 33. squoosh. app — compress any image 34. similarsites. com — find similar websites 35. shortcuts. design — design shortcuts list

Writing microservices “in production” is mostly understanding and building around the failure patterns. 1. Timeouts + retries with jitter. No infinite retries. Cap at 2 to 3. 2. Idempotency keys on every write endpoint. Assume clients will resend. 3. Circuit breaker + bulkheads. One slow dependency shouldn’t take the whole fleet. 4. Outbox pattern for events. Stop doing “write DB then publish” in 2 steps. 5. Rate limits and backpressure. Protect downstreams, shed load early. 6. DLQ + replay tooling. no replay means you’re not event-driven, you’re just hoping. 7. Correlation IDs + tracing. Because if you can’t debug p95 in 10 minutes, you’ll bleed hours.

Your service is healthy until the dependency it calls starts failing. Without protection, failure spreads. That is why the Circuit Breaker Pattern exists 👇 Circuit Breaker Pattern prevents a system from repeatedly calling a failing service. Instead of continuously retrying and exhausting resources, it “breaks the circuit” and stops calls temporarily. It is inspired by electrical circuit breakers. The problem Service A calls Service B. Service B becomes slow or starts returning errors. If A keeps retrying: - Threads get blocked - Connection pools get exhausted - Latency increases - Failure cascades One failing dependency can bring down the entire system. How Circuit Breaker works It has three states: 1. Closed → Normal operation. Requests flow normally. Failures are monitored. 2. Open → Failure threshold exceeded. Requests fail immediately without calling the dependency. 3. Half-Open → After a timeout, a few test requests are allowed.If successful → switch to Closed.If failures continue → go back to Open. Why it matters - Prevents cascading failures - Protects system resources - Improves overall resilience - Fails fast instead of hanging Failing fast is often safer than retrying blindly. When to use it - Microservices architecture - External API integrations - Payment gateways - Database or cache dependencies - High-traffic distributed systems Avoid it in simple monoliths without remote dependencies. Circuit Breaker does not prevent failure. It prevents failure from spreading. Resilience is not about avoiding outages. It is about containing them.

An API Gateway is not just a reverse proxy. It’s the control plane in front of your services. If you’re building microservices and don’t have one, your architecture will eventually get messy. Here’s what it actually does 👇 What is an API Gateway? It’s a single entry point that sits between clients and your backend services. Instead of: Client → Service A Client → Service B Client → Service C You have: Client → API Gateway → Internal Services The gateway handles cross-cutting concerns so your services don’t have to. What does it do? An API Gateway typically handles authentication, authorization, rate limiting, request routing, response aggregation, logging, monitoring, and sometimes caching. It can: - Validate JWT tokens - Enforce rate limits - Route /users to User Service - Route /payments to Payment Service - Combine multiple service responses into one Your microservices stay focused on business logic. When do you need it? You likely need an API Gateway when: - You have multiple microservices - You want centralized authentication - You need rate limiting at the edge - You want to hide internal service structure - You are exposing public APIs If you have a simple monolith, you probably don’t need one yet. Common real-world examples: Netflix, Amazon, and most SaaS platforms use API gateways to manage traffic at scale. Popular solutions include: - NGINX - Kong - AWS API Gateway - Envoy Without an API Gateway: Every service reimplements auth, logging, and rate limiting. With an API Gateway: Infrastructure concerns are centralized and standardized. It’s not just traffic routing. It’s architecture discipline. Building microservices? Repost. Follow. Bookmark this.

@jha186 @venom1s Which area in Jamshedpur ? In Vijaya Garden its over 60 L for 2 BHK.

@venom1s Come to jamshedpur we are selling 2Bhk at 24.30 lakhs , 810 per sq feet ,2 flats available

Guys, is there a city where you can buy a 2BHK house for around 20–40 lakhs?

@krunalexplores Please remove the blue tick (paid) == Hence proved

Hard truth: 99% of creators don’t have a growth problem. They have a discipline problem. You don’t need: • A new niche • A better logo • A paid course You need to post. Every. Single. Day. I did it for 30 days. 2.6M impressions. 63.7K engagements. 2.4K bookmarks. No hacks. No luck. Just consistency. If you’re still “planning” instead of posting… That’s the real reason you’re invisible. Prove me wrong 👇 #BuildInPublic

Pessimistic vs Optimistic Locking Frequently asked Backend interview question [Pessimistic Locking]:- - The record is unavailable to other threads until the current thread finishes working with it. - Even reading the data by other threads is impossible until the lock is removed. - Example: EntityManager.lock(entity, LockModeType.PESSIMISTIC_WRITE) in JPA. - Disadvantages: reduces productivity with a high level of concurrent access. - When to use: when there is a critical need for data accuracy. [Optimistic Locking]:- - Does not block the data when reading, but checks the version of the record when saving. - Example: the @Version annotation in JPA (a column for storing the version). - If the version is changed by another thread, an OptimisticLockException is thrown. - Disadvantages: requires conflict resolution. - When to use: with a large number of reads and a low probability of conflicts. Which approach do you use most often in your projects?

Java 25: an upgrade that saves up to 30% of RAM (without code modifications) In JDK 25, one of the most significant optimizations in a long time was introduced - Compact Object Headers (JEP 519). What changes: - The size of the object header is reduced from approximately ~12 bytes to 8 bytes - Less memory per object = less heap - Less heap = less pressure on the GC - Less GC = faster service + cheaper cloud Where the benefit is maximum: Spring Boot, microservices, DTOs, records, caches - everything where there are a lot of small objects. It's enabled with one option: -XX:+UseCompactObjectHeaders According to reviews in real systems: A 15–30% reduction in heap is a common occurrence. Just test it on your own services - and reap the free savings.

As a Java developer, Please learn: 1. Core Java Mastery - OOP principles (SOLID, DRY, KISS) - Generics, Lambda expressions, Functional interfaces - Java Streams API (map/reduce, collectors) - Java Collections framework - Java Reflection API - Exception handling 2. Multithreading & Concurrency - Thread synchronization, Executors, Locks - Fork/Join framework - Understanding of race conditions, deadlocks, and thread pools - Concurrency utilities (java.util.concurrent) 3. Design Patterns & Architecture - Common design patterns (Singleton, Factory, Builder) - Architectural patterns (MVC, - Microservices, Event-Driven Architecture) - Dependency Injection (DI), Inversion of Control (IoC) 4. Java Memory Management - Garbage Collection (G1, CMS, ZGC) - JVM heap and stack management - Profiling tools (JProfiler, VisualVM) - Analyzing memory leaks, thread dumps, and heap dumps 5. Classloaders and Reflection - Custom class loaders - Dynamic class loading - Reflection for runtime behavior manipulation 6. Spring Framework & Spring Boot - Spring Core (Dependency Injection, AOP) - Spring Boot (Auto-configuration, Microservices support) - Spring Security (OAuth2, JWT) - Spring Data (JPA, Hibernate integration) - Spring Cloud (Netflix OSS, Circuit Breakers) 7. Microservices Architecture - Service discovery (Eureka, Consul) - Load balancing, distributed tracing, and circuit breaking - API Gateway (Zuul, NGINX) - Asynchronous communication with Kafka, RabbitMQ 8. RESTful Web Services - REST principles, building APIs - JSON/XML handling - API versioning, OpenAPI/Swagger documentation 9. Java I/O and NIO - Blocking vs non-blocking I/O (NIO) - Asynchronous I/O, channels, selectors - File handling, serialization and deserialization 10. Reactive Programming - Project Reactor, RxJava - Event-driven architecture, backpressure - Reactive streams, non-blocking IO 11. JPA/Hibernate - ORM principles, entity relationships - Lazy vs eager loading - Caching strategies, query optimization 12. Database Optimization - SQL optimization, indexing, and transactions - NoSQL databases (MongoDB, Cassandra) - ACID principles, CAP theorem 13. Distributed Systems - Consistency, availability, partitioning (CAP) - Event sourcing, CQRS (Command Query Responsibility Segregation) - Distributed caching (Redis, Hazelcast) - Tools: Apache ZooKeeper, Consul, etcd 14. Testing & TDD/BDD - Unit testing (JUnit, Mockito) - Integration and functional testing - Behavior-driven development (Cucumber) 15. CI/CD & DevOps - Continuous integration (Jenkins, CircleCI) - Containerization with Docker - Orchestration with Kubernetes - Source control (Git), versioning, branching strategies 16. Performance Tuning & Optimization - JVM tuning, garbage collection optimization - Caching strategies, load balancing -Tools for profiling and monitoring (Prometheus, Grafana) 17. Security - Authentication/authorization (OAuth2, JWT) - Secure coding (OWASP guidelines) - Encryption (TLS/SSL), CSRF/XSS prevention 18. Cloud Platforms & API Gateways - AWS, Azure, GCP deployment -API Gateway (Zuul, NGINX) for rate-limiting and routing - Cloud-native microservices tools 19. Logging & Monitoring - Centralized logging (ELK Stack, Graylog) - Distributed tracing (Jaeger, Zipkin) - Application Performance Monitoring (APM) 20. Caching Mechanisms - In-memory caching (Ehcache, Caffeine) - Distributed caching (Redis, Memcached) - Cache invalidation strategies (LRU, LFU) 21. Build Tools - Maven and Gradle for dependency management - Multi-module project handling - Continuous delivery pipelines 22. Message Queuing Systems - Kafka, RabbitMQ for event-driven microservices - Pub/Sub models, distributed message brokers

Java devs, how many of these skills are on your CV? 1. Distributed Caching : Redis, Memcache 2. Monitoring : Splunk, Dynatrace, Grafana, ELK 3. Messaging : Kafka, JMS, RabbitMQ 4. Testing : TDD, Mockito, JUnit 5. CI/CD & Containers : Jenkins, GitHub Actions, Docker, Kubernetes 6. Frameworks : Spring Boot, Spring MVC, Apache Camel 7. Microservices : Config Server, API Gateway, Service Discovery, Resilience4j 8. Multithreading & Concurrency : Executors, ForkJoin, CompletableFuture 9. Security : Spring Security, OAuth2, JWT 10. Persistence : Hibernate, JPA, MyBatis 11. API Development : REST, Swagger, OpenAPI 12. Reactive Programming : WebFlux, RxJava, Reactor 13. Build Tools : Maven, Gradle 14. Code Quality : SonarQube, PMD, Checkstyle 15. Cloud : AWS, GCP, Azure 16. Java Versions : Java 8:21 features 17. Design Principles : SOLID, Design Patterns, Clean Architecture

@0xlelouch_ Are both your friends married and have kids ? This will change the scenario u mentioned. I'm in the same boat (both A & B) Friend A will be saving min - 5k $ monthly salary(in-hand, min) - 9.5 - 10k spends: rent - 1,000 - 1.2k car ins - 400 food basic - 600 misc - 2k

Two friends, same goal: buy a ₹1.5 Cr home in Pune. Friend A works in the USA. $160K salary, but after taxes + rent + car + insurance, he saves ~$2.5K/month. He also wires money to India and loses a bit on FX + transfers. Down payment ₹30L takes ~3–4 years if nothing goes wrong. Friend B works in India. ₹45 LPA, saves ₹1.2L/month because parents support, no $3K rent, no surprise medical bills, cheaper life. Down payment ₹30L takes ~2 years. Same house in India, but the math is different: in the USA you earn more, but burn more. In India you earn less, but if your expenses stay low, you can build the down payment faster. We shouldn't compare salaries but compare monthly surplus and timeline to down payment. Would like to know other experiences and how does this work out in the end!

What I see in most Java resumes: - Java - Spring - Microservices Great, I see you know Java. But as a senior, can you build, run, scale, observe, and secure Java systems in production? A few tips and topics with accurate subskills that you need to mention if you need your resume to stand out: 1. Distributed Caching – mention Redis/Memcached 2. Monitoring & Observability – most popular ones are Splunk, Dynatrace, Grafana, ELK 3. Messaging – list one among Kafka, JMS or RabbitMQ 4. Testing – most popular frameworks/methods are TDD, Mockito, JUnit 5. CI/CD & Containers – devops skills like Jenkins, GitHub Actions, Docker, Kubernetes make your profile distinct 6. Frameworks – no prize for guessing: Spring Boot, Spring MVC, Apache Camel 7. Microservices Internals – try to mention one or two at least from Config Server, API Gateway, Service Discovery, Resilience4j 8. Multithreading & Concurrency – do not skip, mention a few of Executors, ForkJoin, CompletableFuture 9. Security – most used and popular ones are Spring Security, OAuth2, JWT 10. Persistence – you should have been using Hibernate, JPA or MyBatis so put one 11. API Development – basics of APIs: REST, Swagger, OpenAPI 12. Reactive Programming – your resume shines with words like WebFlux, Reactor or RxJava 13. Build Tools – mention Maven/Gradle 14. Code Quality – mentioning SonarQube, PMD, Checkstyle shows you care about quality 15. Cloud – shouldn't miss one from AWS, GCP, Azure 16. Java Versions – list a few Java 8 to 21 features you used 17. Design Principles – foundations of large codebase: SOLID, Design Patterns, Clean Architecture If you are targeting Senior, Staff, or Lead roles: - Focus on impact, not buzzwords - Show production ownership - Highlight architecture and reliability thinking Good luck

@IndianTechGuide Is L1 visa stamping slots available ?

🚨 US consulates across India have pushed H-1B visa-stamping interview dates to 2027. No new H-1B stamping in 2026 for Indian professionals.

@akhil__ravula @haristic @money_theory why *60 ?

@haristic @money_theory 80L*0.049*60/365 ~ 65k

If you got ₹1 Cr today, what would you do? 90% will: Buy a house (₹75L locked, EMI trap) Get a new car (₹25L gone instantly) Spend on lifestyle (₹0 left to invest) The 1% play it differently: Invest ₹1 Cr to generate ₹50K–₹1L/month Use cash flow for luxuries, not salary Keep working, stay rich The difference isn’t money. It’s the mindset. Who do you want to be?

If you have 2+ years exp in Java. Don't skip these 6 multithreading problems 👇 1. Producer-Consumer : Use BlockingQueue or wait/notify. 2. Print 1–100 (2 Threads) : Alternate using shared counter + lock 3. Print “ABCABC...” : Sync 3 threads with Lock or notifyAll. 4. Custom Thread Pool : Build using worker threads + queue. 5. Deadlock Scenario : Simulate & prevent via lock ordering. 6. Rate Limiter : Implement Token/Leaky Bucket logic.

@theprabhakars How to open nestro bank account ?

Nostro Account | Banking Concept in Simple Words ○ A Nostro Account is a bank account a domestic bank holds in a foreign bank ○ It is maintained in the foreign currency ○ Used for forex transactions and international trade settlement Example ○ An Indian bank maintains a USD account with a US bank to pay clients in the US Related Term ○ Vostro Account means a foreign bank’s account held in a domestic bank Smart banking runs on such invisible systems #Forex #InternationalTrade

❌ NEVER BUY A PROPERTY IN INDIA WITHOUT THESE DOCUMENTS! Bookmark it🔖 1. TITLE DEED Proves that the seller is the legal owner and has the right to sell the property. 2. MOTHER DEED Shows the complete history of ownership and helps verify that the title is legally traceable. 3. ENCUMBRANCE CERTIFICATE Confirms whether the property is free from loans, mortgages, or legal claims. 4. POSSESSION CERTIFICATE Confirms who is in actual physical possession of the property. 5. PROPERTY TAX RECEIPTS Indicates regular tax payment and absence of local authority dues. 6. KHATA / PATTA CERTIFICATES Reflects the property’s entry in government and municipal records. 7. CONVERSION CERTIFICATE Confirms that the land has been legally converted from agricultural to non-agricultural use, making construction and sale lawful. 8. LOCATION SKETCH & SURVEY MAP Identifies exact boundaries and prevents boundary or survey disputes.

As a backend dev in 2026 , learn these 11 skills to keep you relevant in this Job market : 1. API Design - REST/gRPC 2. Authentication & Authorization - OAuth2, JWT, OpenID Connect, Passkeys 3. Databases - SQL, NoSQL, sharding, indexing, query tuning 4. Caching - Redis, CDN, edge caching strategies 5. Event-Driven Systems - Kafka, Pulsar, streaming pipelines 6. Concurrency & Async - reactive programming, structured concurrency 7. Distributed Systems - microservices, service mesh, eventual consistency 8. Security - HTTPS, encryption, zero trust, OWASP top 10 9. Observability - logging, tracing, metrics, OpenTelemetry 10. Cloud & Deployment - Docker, Kubernetes, serverless, GitOps 11. AI Integration - LLM APIs, vector databases, retrieval-augmented systems Stop jumping from one language to another.

Java platform threads have 6 states. Virtual threads have 20, but they are hidden from us. In my latest newsletter, we show how we can use deep reflection to figure out how this all holds together: javaspecialists.eu/archive/Issue3… (Make sure to subscribe to not miss a single issue) @java #Java