Codewell alex (9 Ergebnisse)
- Softcover
Anbieter: Ria Christie Collections, Uxbridge, Vereinigtes KönigreichRia Christie Collections
Verkäufer/-in kontaktierenVerkäufer/-in mit 5 SternenZustand: Neu
EUR 12,21
EUR 13,98 VersandVersand von Vereinigtes Königreich nach USAAnzahl: Mehr als 20 verfügbar
Zustand: New. In.
- Softcover
Anbieter: AHA-BUCH GmbH, Einbeck, DeutschlandAHA-BUCH GmbH
Verkäufer/-in kontaktierenVerkäufer/-in mit 5 SternenZustand: Neu
EUR 26,70
EUR 61,21 VersandVersand von Deutschland nach USAAnzahl: 2 verfügbar
Taschenbuch. Zustand: Neu. Neuware - What if the automation you built to save your developers is actually the reason they are burning out Platform engineering was supposed to fix DevOps. Instead, many organizations replaced operations silos with cognitive overload, ticket queues, and YAML fatigue. This book examines why your int…ernal tooling exists, why your developers avoid it, and how to rebuild it as a product they actually want to use. Drawing on real organizational audits and systems design principles, it exposes the maturity trap that turned 'you build it, you run it' into a burnout engine-and maps a precise way out that treats developer experience as a hard systems constraint, not a marketing slogan. You will learn why the bottleneck shifted from hardware scarcity to attention scarcity, and why every new abstraction added another leak in the cognitive dam.Inside, you will find: - Why operational responsibility without operational capability fragments expertise and breeds shadow IT across teams- The hidden cost of context switching: how a 4.7-hour weekly ticket tax silently destroys lead times and architectural quality- Why Kubernetes, service mesh, and policy-as-code created an accretion layer of complexity that senior engineers now navigate instead of shipping features- How to treat your internal platform as a product, with user research, guardrails, and self-service paths that make the right choice obvious- The architectural contracts, APIs, and cognitive guardrails that reduce mental load without surrendering governance, compliance, or securityIf you are an engineering leader watching deployment frequency drop while incident retrospectives multiply, this book offers the architectural framework to rebuild your delivery pipeline around attention scarcity, not hardware scarcity. Stop manualizing interactions with your own automation. Start building internal platforms that respect the limits of working memory-and watch your teams ship faster, safer, and with less friction. Your platform team is not a help desk. It is a product team. Time to build like one.
- Softcover
Anbieter: AHA-BUCH GmbH, Einbeck, DeutschlandAHA-BUCH GmbH
Verkäufer/-in kontaktierenVerkäufer/-in mit 5 SternenZustand: Neu
EUR 29,59
EUR 61,18 VersandVersand von Deutschland nach USAAnzahl: 2 verfügbar
Taschenbuch. Zustand: Neu. Neuware.
- Softcover
Anbieter: AHA-BUCH GmbH, Einbeck, DeutschlandAHA-BUCH GmbH
Verkäufer/-in kontaktierenVerkäufer/-in mit 5 SternenZustand: Neu
EUR 33,40
EUR 61,60 VersandVersand von Deutschland nach USAAnzahl: 2 verfügbar
Taschenbuch. Zustand: Neu. Neuware - What happens when your most critical system fails and the only person who understood it left six months ago Every engineering team carries silent debt-not in the codebase, but in the documentation that was never written, never updated, or buried so deep it might as well not exist. API endpoin…ts return 404s in their own example sections. Architecture diagrams describe services that no longer run. Runbooks assume knowledge that walked out the door with the last senior engineer. The cost is no longer mild frustration. It is production incidents, delayed launches, and talent attrition.Technical Writing for Engineers treats documentation as an engineering discipline, not a creative writing exercise. You will not find advice on 'finding your voice' or storytelling theory here. You will find systematic methods for communicating technical truth with the same rigor you apply to code review.Inside this book, you will learn how to: - Structure API references that developers actually consult under incident-response pressure-not just during onboarding week one - Diagram architectures that remain accurate after deployment, not just during the initial design review - Embed documentation into your CI/CD pipeline so it stays current the moment code merges, not six sprints later - Write for scanning behaviors, using progressive disclosure so engineers find the answer in seconds, not paragraphs - Measure the return on investment of your documentation workflow and prove its value to leadership - Apply AI-assisted tooling to maintain consistency across distributed teams without ballooning overheadWritten for backend engineers, platform architects, DevOps leads, and anyone who has groaned when assigned to 'update the docs,' this book provides templates, specification references, and anti-patterns you can apply to your next commit.Your systems are only as maintainable as the documentation that explains them. Stop treating technical writing as someone else's responsibility. Get your copy today and turn your documentation from organizational liability into critical infrastructure.
- Softcover
Anbieter: AHA-BUCH GmbH, Einbeck, DeutschlandAHA-BUCH GmbH
Verkäufer/-in kontaktierenVerkäufer/-in mit 5 SternenZustand: Neu
EUR 41,49
EUR 62,58 VersandVersand von Deutschland nach USAAnzahl: 2 verfügbar
Taschenbuch. Zustand: Neu. Neuware - What separates data pipelines that survive Friday night deployments from those that collapse before Monday morning Most Python developers can write scripts that process CSV files. Few can build systems that handle API timeouts, schema drift, and that 2 AM alert when the CFO's dashboard shows…$40,000 in missing revenue. This book bridges that gap with fifteen years of battle-tested engineering wisdom drawn from hedge funds, health-tech startups, and Fortune 500 retailers.Inside, you will learn how to: - Build ETL pipelines that fail predictably, recover automatically, and alert meaningfully-before stakeholders notice- Design warehouse schemas that handle real-world data quality issues without requiring midnight refactoring- Implement real-time streaming with Kafka and Python that survives Unicode exceptions and rate-limit storms- Apply testing strategies and type safety that prevent the 3 AM debugging sessions every data engineer dreads- Control costs and observability across cloud infrastructure so your pipelines outlast your tenureEvery pattern here has been tested against actual latency requirements, budget constraints, and stakeholders who change specifications mid-quarter. The code is complete, runnable, and intentionally imperfect-showing the retry logic, workarounds, and memory optimizations that production demands.Data engineering is not about elegant syntax. It is about writing defensible systems that handle upstream failures, downstream schema changes, and the inevitable moment when someone uploads the wrong file at the worst possible time.If you are ready to move from writing scripts to owning infrastructure that powers business decisions, this manual gives you the frameworks, failure patterns, and operational rigor to do exactly that. Your pipelines will not just run. They will endure.Get your copy today and build data systems that last-starting with your very next deployment.
- Softcover
Anbieter: AHA-BUCH GmbH, Einbeck, DeutschlandAHA-BUCH GmbH
Verkäufer/-in kontaktierenVerkäufer/-in mit 5 SternenZustand: Neu
EUR 42,50
EUR 63,11 VersandVersand von Deutschland nach USAAnzahl: 2 verfügbar
Taschenbuch. Zustand: Neu. Neuware - Kubernetes dominates container orchestration because it solved a real problem: human operators cannot manually place, recover, and scale workloads across hundreds of nodes. Yet the system that eliminated one layer of complexity introduced another. Born from Google's Borg but stripped of its h…omogeneous, privileged environment, Kubernetes evolved into a modular federation of semi-independent components-each with distinct failure modes, version cycles, and vendor priorities.This book examines Kubernetes not as a finished product, but as an ongoing architectural compromise. You will learn why the Container Runtime, Network, and Storage interfaces that freed the ecosystem from vendor lock-in simultaneously created unpredictable latency surfaces and policy conflicts. You will see how scheduler decisions collide with resource quotas, how network overlays amplify latency under pressure, and how autoscaling controllers can trigger destabilizing feedback loops. Through production postmortems from large-scale environments, the text reveals why workload failures are rarely singular-and why reasoning about cascading interactions is now the central skill of platform engineering.The book also confronts unresolved scaling tensions. Kubernetes was originally optimized for clusters of thousands of nodes; modern environments routinely exceed that boundary, forcing painful choices between vertical cluster growth and multi-cluster coordination. It traces the shift from treating clusters as permanent infrastructure to viewing them as disposable scheduling domains-a conceptual change that redefines reliability engineering for cloud-native systems.What You Will Learn - Why Kubernetes rejected Mesos's two-level scheduling-and how that centralized decision created today's fairness and preemption challenges - How CRI, CNI, and CSI abstractions solved vendor politics while fragmenting operational predictability - The real reason production postmortems blame interaction patterns, not individual components - Why autoscaling, resource quotas, and network overlays form a hidden feedback loop that can destabilize utilization - The architectural entropy created by admission controllers, custom resource definitions, and policy engines - When to scale vertically versus distributing across clusters, and why hybrid federation is becoming the dominant patternIf your team runs production Kubernetes at scale, this book delivers the architectural clarity and operational rigor to build systems that fail gracefully rather than catastrophically. Read it before your next postmortem.
- Softcover
Anbieter: AHA-BUCH GmbH, Einbeck, DeutschlandAHA-BUCH GmbH
Verkäufer/-in kontaktierenVerkäufer/-in mit 5 SternenZustand: Neu
EUR 43,52
EUR 63,63 VersandVersand von Deutschland nach USAAnzahl: 2 verfügbar
Taschenbuch. Zustand: Neu. Neuware - What separates systems that survive credential breaches from those that collapse under them The answer lies not in better frameworks, but in architectural decisions made before the first auth endpoint is deployed.Every request hitting your application asks the same critical question: Should t…his be allowed Answered thousands of times per second, this question defines the boundary between secure operations and catastrophic exposure. Yet most organizations still apply monolithic auth patterns to distributed systems serving millions of concurrent users. The consequences are entirely measurable-leaked JWTs through client-side storage, stale role data propagating across microservices, API keys buried in repositories years after employee departure, and authorization checks that crumble under production load.This book provides the architectural field manual that engineering teams have lacked. Drawing from production-tested patterns across high-throughput microservice meshes and multi-tenant SaaS platforms, it bridges the persistent gap between security theory and implementable, observable systems.Inside, you will find: - How to map STRIDE threat categories onto authentication flows before committing the first line of authorization code - Session distribution strategies across Kubernetes clusters that maintain strong consistency without introducing latency bottlenecks - Refresh token rotation patterns that detect family theft in real-time distributed environments - Comparative analysis of Zanzibar-style relationship databases versus XACML policy engines with production-tested decision frameworks - Architectural implications of adopting FIDO2 passkeys in consumer applications versus SAML in enterprise contexts - Operational guidance on secret rotation, compliance automation, and monitoring that separates fragile proofs-of-concept from enterprise-grade infrastructureWritten for senior backend engineers, security architects, and platform engineers who have shipped production web applications, this guide moves past tutorial-level explanations to examine precisely how tokens should be validated, cached, and revoked at scale.Your applications are already being probed. Build the access control architecture that responds with certainty rather than hope.
- Softcover
Anbieter: AHA-BUCH GmbH, Einbeck, DeutschlandAHA-BUCH GmbH
Verkäufer/-in kontaktierenVerkäufer/-in mit 5 SternenZustand: Neu
EUR 47,56
EUR 62,81 VersandVersand von Deutschland nach USAAnzahl: 2 verfügbar
Taschenbuch. Zustand: Neu. Neuware - Rust Systems Programming: Memory Safety, Concurrency & Embedded Applications.What if the compiler could catch the memory errors that cost the industry billions-before a single line of your code reached production Rust is not merely another systems language. It is a paradigm shift that rejects… the false choice between safety and speed. This book is written for the engineer who has shipped production C but lies awake thinking about that unchecked pointer; for the firmware developer exhausted by vendor lock-in; for the architect choosing the language that will define the next decade of infrastructure. Spanning bare-metal ARM Cortex-M and RISC-V microcontrollers to high-performance concurrent servers, the text organizes its guidance into five progressive parts-ownership semantics, fearless concurrency, controlled unsafe, embedded architecture, and production-grade deployment.Inside, you will find: - How Rust's borrow checker functions as a formal verification system-enforcing, at compile time, the memory discipline that expert C programmers spend careers internalizing- Why zero-cost abstractions and deterministic resource management position Rust to break the embedded expertise bottleneck without sacrificing real-time guarantees- How to build a memory-safe device driver that uses Rust's type system to enforce correct state transitions at compile time- The architectural patterns behind a lock-free real-time data acquisition system, a minimal TCP/IP stack with zero-copy networking, and an async runtime built for resource-constrained environments- A rigorous treatment of unsafe as a controlled interface-not a forbidden zone-plus deterministic testing, secure boot, and over-the-air update strategies for production firmwareIf you believe segfaults are not an inevitable tax on systems programming, this book provides the architectural depth and production-grade examples to prove it. Stop trusting human discipline alone to manage memory. Start writing systems that are fast by design and safe by construction-from bare-metal microcontrollers to concurrent servers. The tools have changed. Your code should too.
- Softcover
Anbieter: AHA-BUCH GmbH, Einbeck, DeutschlandAHA-BUCH GmbH
Verkäufer/-in kontaktierenVerkäufer/-in mit 5 SternenZustand: Neu
EUR 52,03
EUR 64,84 VersandVersand von Deutschland nach USAAnzahl: 2 verfügbar
Taschenbuch. Zustand: Neu. Neuware - What if the network perimeter you spent years building has already become the attacker's highway In cloud-native environments, containers migrate across hosts, serverless functions exist for milliseconds, and APIs communicate across organizational boundaries. The castle walls of traditional s…ecurity-firewalls, VLANs, and private subnets-no longer protect what matters. An S3 misconfiguration, a cached CI credential, or a compromised developer laptop can bypass every network control you have architected.This book bridges the gap between Zero Trust philosophy and production-grade implementation. Written from the trenches by a cloud security architect who has responded to breaches at 3 AM, it treats Zero Trust not as a product category, but as an engineering discipline.Inside, you will learn: - Why most 'Zero Trust' rollouts are merely security theater-and how to spot the gaps before attackers do - How identity becomes your true perimeter when workloads are ephemeral and boundaries dissolve - The architectural patterns that make SPIFFE identities, OPA policies, and mTLS meshes work as a unified system - Why continuous verification beats one-time authentication when protecting financial transactions, healthcare data, and critical infrastructureFor platform engineers, security architects, and DevSecOps teams, this is the systematic framework you need to build resilient systems where compromise is assumed, authorization is granular, and verification never stops.The perimeter is dead. Architect what comes next-get your copy today.
