Chekkal Samir (53 results)

Condition: As New. Unread book in perfect condition.

Condition: New.

Condition: New.

Condition: New.

Condition: As New. Unread book in perfect condition.

Condition: As New. Unread book in perfect condition.

Condition: New.

Condition: As New. Unread book in perfect condition.

Condition: New.

Condition: New.

Condition: As New. Unread book in perfect condition.

Condition: As New. Unread book in perfect condition.

Taschenbuch. Condition: Neu. Neuware - The self-help bestsellers of the last twenty years are fragments of one system. This book reassembles it. Look at your shelf. The book that told you to stop caring what other people think. The one that told you your attention is being harvested. The one about why you sabotage yourself the moment life improves. The one about surrender. The one about manifesting. Each produced two electric weeks - and then faded like a gym membership in February. Here is what nobody in publishing says out loud: those books are not different books. Each is one genuine insight, given a sticky name and stretched to 250 pages. And each one, alone, has a failure mode its own book cannot explain. When does 'letting them' become letting people walk over you When does surrender become drift When does visualizing replace acting You felt those edges yourself - they are exactly where the two weeks ended. A rule tells you what to do. Only a mechanism tells you when it stops working. In 2004, a Russian author writing under the name Vadim Zeland published a five-volume system that contains a recognizable, interlocked version of nearly every rule on your shelf - most of it written before the smartphone existed. This book is an independent work of commentary and analysis: a guide to that machine, entered through the doors you already own. If you have read the big single-idea books of the last decade - on letting other people be, on defending your attention, on the self-sabotage that follows success, on surrender, on manifesting - this book is the wiring diagram they were missing. Every chapter runs the same four-stroke cycle: - The Fragment - the famous rule, stated fairly, with full credit to its author- The Whole Mechanism - the larger moving part it was carved from, in plain English- What the Fragment Misses - the failure mode you already experienced, and why the mechanism predicts it- The Practice - one concrete exercise that uses the whole part, not the piece Then Part 3 assembles everything into a single daily operating loop, a 30-day installation protocol, and an unsparing skeptic's chapter on how this system fails and how its own fans abuse it. An honest book about a strange one. This is not a conspiracy story - nobody copied anyone. Independent authors kept converging on pieces of the same machine - and Zeland built its most complete assembly in one place. No metaphysics is required of you: every mechanism is restated as practical psychology - attention, expectation, self-image, behavior - and the practices are the same under every interpretation. Your shelf was never wrong. It was incomplete. Stop thinking you need another book. Read the one behind all of them.…

Paperback. Condition: new. Paperback. The self-help bestsellers of the last twenty years are fragments of one system. This book reassembles it. Look at your shelf. The book that told you to stop caring what other people think. The one that told you your attention is being harvested. The one about why you sabotage yourself the moment life improves. The one about surrender. The one about manifesting. Each produced two electric weeks - and then faded like a gym membership in February. Here is what nobody in publishing says out loud: those books are not different books. Each is one genuine insight, given a sticky name and stretched to 250 pages. And each one, alone, has a failure mode its own book cannot explain. When does "letting them" become letting people walk over you? When does surrender become drift? When does visualizing replace acting? You felt those edges yourself - they are exactly where the two weeks ended. A rule tells you what to do. Only a mechanism tells you when it stops working. In 2004, a Russian author writing under the name Vadim Zeland published a five-volume system that contains a recognizable, interlocked version of nearly every rule on your shelf - most of it written before the smartphone existed. This book is an independent work of commentary and analysis: a guide to that machine, entered through the doors you already own. If you have read the big single-idea books of the last decade - on letting other people be, on defending your attention, on the self-sabotage that follows success, on surrender, on manifesting - this book is the wiring diagram they were missing. Every chapter runs the same four-stroke cycle: - The Fragment - the famous rule, stated fairly, with full credit to its author- The Whole Mechanism - the larger moving part it was carved from, in plain English- What the Fragment Misses - the failure mode you already experienced, and why the mechanism predicts it- The Practice - one concrete exercise that uses the whole part, not the piece Then Part 3 assembles everything into a single daily operating loop, a 30-day installation protocol, and an unsparing skeptic's chapter on how this system fails and how its own fans abuse it. An honest book about a strange one. This is not a conspiracy story - nobody copied anyone. Independent authors kept converging on pieces of the same machine - and Zeland built its most complete assembly in one place. No metaphysics is required of you: every mechanism is restated as practical psychology - attention, expectation, self-image, behavior - and the practices are the same under every interpretation. Your shelf was never wrong. It was incomplete. Stop thinking you need another book. Read the one behind all of them. This item is printed on demand. Shipping may be from multiple locations in the US or from the UK, depending on stock availability.…

PAP. Condition: New. New Book. Shipped from UK. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000.

Taschenbuch. Condition: Neu. Neuware - You can run traceroute. Can you explain why it works Every networking tool is applied protocol semantics. It repurposes a field, or exploits a behavior the RFC either mandated or left undefined. Traceroute is the TTL field doing a second job. The nmap SYN, FIN, NULL, Xmas, and ACK scans are RFC 793's own mandated replies turned into a probe. The idle scan reads a stranger's IP ID counter. p0f fingerprints a host from the idiosyncrasies of its TCP options. The Kaminsky attack races sixteen bits of DNS entropy. TCP/IP in Practice teaches the stack the way an engineer actually learns it: by understanding why each tool works, field by field, and then inverting every mechanism into a defense. For each technique, the book shows the defensive inversion the protocol community actually shipped - SYN cookies, GTSM, RFC 6528 sequence numbers, source-port randomization, DNS 0x20 encoding, response-rate limiting, and uRPF - as one coherent family rather than a list of unrelated fixes. Who it is for>Inside- The field-by-field core. TTL and path shape, the handshake's honest answers, ISN entropy and spoofing, the IP ID side channel, and timestamp/window/option fingerprinting - each derived from the RFC.- The tool families. ARP and the blind network map, active and passive fingerprinting, UDP and ICMP inference, fragment-based evasion, covert channels, and DNS cache poisoning.- The defensive inversions, assembled. Encode state in the field, add entropy, verify the field - one meta-pattern behind every modern defense.- A hands-on lab. A self-contained Linux network-namespace testbed built with Scapy, hping3, tcpdump, and Wireshark. You reconstruct traceroute, a SYN scanner, the idle scan, a p0f-lite classifier, and a DNS-poisoning proof of concept - each in about a dozen lines.- Six graded katas, from mapping a subnet you cannot send traffic to, to redesigning a technique the defenders already killed.Thirty-one chapters, eighteen hand-drawn diagrams, and four appendices - including a field ? tool ? defense quick-reference table. Samir Chekkal is the author of the In Practice series - concise, hands-on guides written by an engineer for engineers who ship real systems. …

PAP. Condition: New. New Book. Delivered from our UK warehouse in 4 to 14 business days. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000.

Condition: New. Print on Demand.

Paperback. Condition: new. Paperback. You can run traceroute. Can you explain why it works? Every networking tool is applied protocol semantics. It repurposes a field, or exploits a behavior the RFC either mandated or left undefined. Traceroute is the TTL field doing a second job. The nmap SYN, FIN, NULL, Xmas, and ACK scans are RFC 793's own mandated replies turned into a probe. The idle scan reads a stranger's IP ID counter. p0f fingerprints a host from the idiosyncrasies of its TCP options. The Kaminsky attack races sixteen bits of DNS entropy. TCP/IP in Practice teaches the stack the way an engineer actually learns it: by understanding why each tool works, field by field, and then inverting every mechanism into a defense. For each technique, the book shows the defensive inversion the protocol community actually shipped - SYN cookies, GTSM, RFC 6528 sequence numbers, source-port randomization, DNS 0x20 encoding, response-rate limiting, and uRPF - as one coherent family rather than a list of unrelated fixes. Who it is forSenior engineers and security practitioners who already use these tools and want to own the mechanism instead of memorizing the command. It assumes you know what an IP packet and a TCP handshake are. It does not assume you have ever opened Scapy. InsideThe field-by-field core. TTL and path shape, the handshake's honest answers, ISN entropy and spoofing, the IP ID side channel, and timestamp/window/option fingerprinting - each derived from the RFC.The tool families. ARP and the blind network map, active and passive fingerprinting, UDP and ICMP inference, fragment-based evasion, covert channels, and DNS cache poisoning.The defensive inversions, assembled. Encode state in the field, add entropy, verify the field - one meta-pattern behind every modern defense.A hands-on lab. A self-contained Linux network-namespace testbed built with Scapy, hping3, tcpdump, and Wireshark. You reconstruct traceroute, a SYN scanner, the idle scan, a p0f-lite classifier, and a DNS-poisoning proof of concept - each in about a dozen lines.Six graded katas, from mapping a subnet you cannot send traffic to, to redesigning a technique the defenders already killed.Thirty-one chapters, eighteen hand-drawn diagrams, and four appendices - including a field tool defense quick-reference table. Samir Chekkal is the author of the In Practice series - concise, hands-on guides written by an engineer for engineers who ship real systems. This item is printed on demand. Shipping may be from multiple locations in the US or from the UK, depending on stock availability. …

PAP. Condition: New. New Book. Shipped from UK. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000.

Paperback. Condition: new. Paperback. The Happiness Engine changes that. Drawing from positive psychology, neuroscience, Stoic philosophy, Sufi wisdom, Hindu and Greek thought, and modern behavioral research, this book presents nine engine components - each grounded in evidence, enriched by wisdom traditions, and made real through embedded practice. This is not a book of abstract ideas. Every chapter includes "try this now" exercises you can do in 30 seconds to 3 minutes, plus end-of-chapter rituals for deeper practice. By the end, you will have both a new way of seeing and a daily practice for living it. This item is printed on demand. Shipping may be from multiple locations in the US or from the UK, depending on stock availability.…

Paperback. Condition: new. Paperback. Microservices architectures push networking concerns out of application code and into the infrastructure layer. Service discovery, load balancing, retries, timeouts, mutual authentication, and traffic shaping all need to work reliably across hundreds of services without requiring every team to implement them independently. Istio solves this by deploying Envoy sidecar proxies alongside every workload, creating a service mesh that handles cross-cutting concerns transparently at the network level. Istio in Practice gives engineers the depth they need to deploy, configure, and operate Istio with confidence. Starting from the control plane architecture and the data plane mechanics of Envoy, the book progresses through traffic management primitives, progressive delivery strategies, security policies, observability integration, and production operations. Each chapter connects architecture to real engineering decisions: how to structure routing rules, how to enforce mutual TLS across namespaces, how to implement canary rollouts safely, and how to debug mesh issues before they become outages. Inside the book, you will learn: - how Istio's control plane configures Envoy sidecars via xDS APIs- how VirtualService, DestinationRule, and Gateway resources control traffic flow- how to implement canary deployments, traffic mirroring, and fault injection- how mutual TLS, authorization policies, and request authentication enforce zero-trust networking- how to integrate Prometheus, Grafana, Jaeger, and Kiali for full-stack observability- how to debug common mesh problems including proxy misconfiguration, certificate rotation failures, and resource exhaustion- how Istio compares to Linkerd, Consul Connect, and cloud-provider service mesh offerings Written for backend engineers, platform architects, and infrastructure teams, this book turns Istio from a complex installation into a well-understood, production-ready networking layer for Kubernetes. This item is printed on demand. Shipping may be from multiple locations in the US or from the UK, depending on stock availability.…

PAP. Condition: New. New Book. Shipped from UK. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000.

Paperback. Condition: new. Paperback. Spring Boot Microservices in Practice is a practical guide for Java developers, software architects, and technical leads who want to design, build, and operate production-grade microservice systems using Spring Boot and the broader Spring ecosystem. Microservices promise independent deployability, resilience, and team autonomy. In practice, the real difficulty begins after the first service is deployed. Teams must deal with service discovery, distributed configuration, inter-service communication, fault tolerance, messaging, data consistency, observability, security, CI/CD, and the platform guardrails needed to keep systems coherent at scale. This book covers the full lifecycle of modern Spring Boot microservices. You will learn how to design services, build APIs, implement synchronous and asynchronous communication, manage messaging with Kafka and RabbitMQ, apply resilience patterns, secure distributed systems, and run services in production with Kubernetes, observability, and deployment automation. Inside the book, you will learn how to: - design Spring Boot microservices with clear boundaries- build REST and reactive APIs- use messaging patterns with Kafka and RabbitMQ- manage distributed configuration and service discovery- apply resilience patterns such as retries, circuit breakers, and bulkheads- secure services with OAuth2, JWT, and Spring Security- instrument systems with metrics, traces, and logs- deploy Spring Boot services to Kubernetes- test microservices with integration, contract, and end-to-end strategies- avoid microservice sprawl with better operating-model guardrails Every chapter is grounded in realistic production concerns, not just toy examples. Whether you are building your first distributed system or improving an existing microservice landscape, this book gives you the implementation patterns and operational practices needed to build reliable Spring Boot services in production. This item is printed on demand. Shipping may be from multiple locations in the US or from the UK, depending on stock availability. …

PAP. Condition: New. New Book. Shipped from UK. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000.

Paperback. Condition: new. Paperback. Build practical observability skills with OpenTelemetry. OpenTelemetry in Practice is a hands-on guide to designing and implementing modern observability in real software systems. It explains how to use traces, metrics, logs, context propagation, and collector pipelines to understand application behavior and troubleshoot productionissues effectively. This book is written for software engineers, SREs, platform engineers, architects, and technical leaders who want to move beyond theory and apply OpenTelemetry in production environments. In this book, you will learn how to: - understand the OpenTelemetry architecture and core building blocks- instrument applications and services for meaningful telemetry- work with traces, metrics, and logs together- use context propagation and correlation across distributed systems- design and operate OpenTelemetry Collector pipelines- export telemetry to observability backends- troubleshoot performance, latency, and reliability issues- apply sampling and telemetry controls in production- use OpenTelemetry in microservices and Kubernetes environments- avoid common implementation mistakes OpenTelemetry has become a key standard for modern observability. This book helps you use it in a practical, implementation-focused way so that you can build better visibility into your systems and respond faster to real operational problems. If you work on cloud-native applications, distributed systems, or platform engineering initiatives, this book will help you apply OpenTelemetry with clarity and confidence. This item is printed on demand. Shipping may be from multiple locations in the US or from the UK, depending on stock availability.…

Paperback. Condition: new. Paperback. Modern software teams say they are empowering developers. In practice, they are often overloading them. The Overloaded Developer examines how the industry gradually pushed testing, operations, security, architecture, documentation, prioritization, alignment, governance, hiring, and on-call work onto the developer role, then called the result agility. The outcome is familiar: slower delivery, weaker quality, rising burnout, and teams that look efficient on paper while quietly getting worse at the work that matters. This book is written for developers, engineering managers, CTOs, and product leaders who sense that something is wrong with the way modern software teams are structured. It combines management analysis, lived engineering experience, and a clear operating-model argument: software organizations do not become stronger by asking one role to absorb the work of many. Inside, you will find: - clear overload patterns across modern engineering work - practical language for making trade-offs visible - role-boundary models for healthier team design - guidance on specialization, cross-functional teams, and platform support - a realistic view of automation, GitOps, and AI as tools to reduce toil rather than excuses to increase overload If you have ever looked at your calendar, your backlog, your on-call load, and your meeting schedule and felt that the role itself had become unreasonable, this book will explain why. If you lead teams, it will show you what a better model looks like. This item is printed on demand. Shipping may be from multiple locations in the US or from the UK, depending on stock availability. …

PAP. Condition: New. New Book. Shipped from UK. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000.

PAP. Condition: New. New Book. Shipped from UK. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000.

PAP. Condition: New. New Book. Shipped from UK. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000.