Private corporate batches, live online cohorts and 1-on-1 mentoring in Apache's Maven-first repository manager — managed and remote repositories, proxy connectors, Redback security, scanning and purge, and an honest comparison against Nexus and Artifactory — taught by a practitioner who runs it in production.
20 years across DevOps, SRE and Security · 10,000+ engineers trained · Trained teams at JPMorgan Chase, Verizon, Nokia and the World Bank
Principal DevOps Engineer & Architect
Rajesh teaches Archiva as repository infrastructure rather than as a web interface: deployment topology and JVM sizing, managed versus remote repositories, proxy connectors and caching behaviour, Redback roles wired to LDAP, scanner consumers and index health, and purge rules tuned to real snapshot volumes. Sessions include the parts that decide whether a repository manager survives — backup and restore, upgrades, disk growth — and an unsentimental comparison against Nexus and Artifactory, including how to migrate off Archiva when that is the right answer.
Twenty years across DevOps, SRE and Security, in principal and architect roles at PayPay, SoftwareAG, ServiceNow, JDA Software, Intuit, Adobe and others. He has trained engineers at JPMorgan Chase, Verizon, Nokia, the World Bank, VMware, Oracle, Mercedes-Benz and Airbus — more than 10,000 people personally. He teaches what he runs, not what he reads.
You are booked with a named engineer, and that is who turns up. Marketplaces and larger providers rotate whoever is free, so the person who sold you the agenda is rarely the person teaching it.
The same trainer is available for the next engagement, which matters when a team builds on what it learned last time.
Your batch is assigned a named trainer before it starts, and that is who teaches it. See the full faculty.
Engagements are matched on the tool, not the calendar. For Apache Archiva that means a trainer who has run it in production — Apache's Maven-first repository manager — managed and remote repositories, proxy connectors, Redback security, scanning and purge, and an honest comparison against Nexus and Artifactory — rather than whoever is free that week. You are told who is teaching before you commit, and that person is on the discovery call that shapes the agenda.
Where a batch is large enough to need a second trainer, the pairing is declared up front. The lead trainer stays accountable for the syllabus and the assessment either way.
Principal DevOps Engineer & Architect
Twenty years across DevOps, SRE and Security in principal and architect roles at PayPay, SoftwareAG, ServiceNow, JDA Software, Intuit, Adobe, IBM/Emptoris, Ness, MindTree and Accenture. He has trained more than 10,000 engineers personally, at organisations including JPMorgan Chase, Verizon, Nokia, the World Bank, VMware, Oracle, Mercedes-Benz and Airbus. He teaches what he runs, not what he reads.
Teams of 8–30
Custom agenda, your timezone, onsite or online, NDA-friendly.
Request a quoteIndividual engineers
A private instructor and a curriculum built around your goal.
₹99,999Individuals who want peers
Scheduled batch, max 8 to 10 hours of live instruction.
₹34,999A private batch starts with a discovery call. We look at the stack you actually run — the CI system, the cloud, the constraints — and map the agenda onto it, so examples use your topology rather than a generic one.
Delivery is onsite at your premises, live online, or hybrid, scheduled around your release calendar rather than ours. Batches run 8 to 30 engineers.
Every attendee leaves with recordings, slides, lab repositories and a completion certificate. You receive an attendance and assessment report. Invoicing supports PO and GST.
Talk to us about a private Apache Archiva batchApache Archiva is a build artifact repository manager from the Apache Software Foundation. It sits between your builds and the outside world, holding two kinds of repository: managed repositories, where your own build output is deployed, and remote repositories, which Archiva proxies and caches on behalf of your builds through proxy connectors. Point a build's settings at Archiva and every dependency it consumes arrives through a server you operate, log and can serve when the upstream is unreachable.
Archiva is a Java application, deployed standalone with an embedded servlet container or as a WAR into an existing one. Security comes from Apache Redback, which supplies users, roles and permissions with optional LDAP or Active Directory authentication, and the permission model is repository-scoped — a role grants observer or manager rights on specific repositories rather than globally. A background scanner walks each repository and hands artifacts to configurable consumers that build search indexes, update metadata, validate layout and detect content that does not belong. Purge rules on each managed repository control how many snapshot versions survive and for how long.
The honest positioning matters. Apache Archiva is Maven-shaped: it does Maven and Ivy-style repository layouts genuinely well, and it does not attempt the format breadth that Nexus Repository and Artifactory offer — there is no first-class Docker registry, npm registry or PyPI index. Its release cadence has been intermittent for several years, so anyone evaluating it today should check the project's current status before committing. For a Maven-only estate that wants a small, self-hosted, Apache-licensed proxy and deployment target, it remains a reasonable and inexpensive choice. For a polyglot estate, it is the wrong tool and this course says so directly.
Two populations need Archiva skills, and they need different things. The first already runs it — frequently a server installed years ago that quietly became critical, with an administrator who has left. Those teams need to operate it properly: upgrades, backup and restore, security configuration, purge rules that stop the disk filling, and proxy connectors that behave when an upstream repository changes its URL or its TLS configuration.
The second population is evaluating repository managers and needs an honest comparison rather than a vendor pitch. Repository managers are not interchangeable: format coverage, high availability, replication, retention policy expressiveness and integration with component-intelligence tooling differ sharply, and the cost of choosing wrong is a migration of every build in the organisation.
Either way the underlying skill is the same and it outlives the product: understanding what a repository manager is for, how proxying and caching change build reliability, how deployment and release promotion should work, and what a retention policy has to guarantee. This course teaches Archiva concretely and that model transferably — including the migration path, because for a meaningful share of teams the correct outcome is to move on.
The problem before the product. Why builds that reach the public internet directly are unreliable and unauditable, what proxying and caching actually buy, and a direct comparison of Archiva against Nexus Repository and Artifactory on format coverage, availability, retention and operational cost.
Topics: What breaks without a repository manager: availability, reproducibility, auditability · Proxy, cache and deployment target — the three jobs of a repository manager · Archiva's architecture: web application, data directory, metadata store, index · Format coverage — where Archiva is Maven-shaped and what that excludes · Archiva versus Nexus Repository and Artifactory, feature by feature · Project activity and release cadence as a selection criterion · When Archiva is the right choice, and when it is not
Getting Archiva running in a way that can be supported a year later. Standalone versus WAR deployment, Java version constraints, separating configuration and data from the installation, JVM sizing against real repository volumes, and terminating TLS in front of it.
Topics: Standalone distribution versus WAR deployment into an existing container · Java version requirements and JVM options that matter · The data directory: repositories, configuration, index and database · Separating installation from data so upgrades are non-destructive · Reverse proxy, TLS termination and base URL configuration · The internal database and the metadata store backends · First-run configuration and the admin account · Logging configuration and where to look when it will not start
The core configuration. Managed repositories for what you publish, remote repositories for what you consume, proxy connectors joining the two, and the policies that decide what happens when an upstream is slow, unreachable or has removed an artifact you already cached.
Topics: Managed repositories: releases, snapshots, staging and third-party · Repository layout, indexing options and scanning schedule · Remote repositories and connecting to Central and vendor repositories · Proxy connectors: ordering, whitelists and blacklists · Connector policies — snapshot handling, release handling, checksum and cache failures · Repository groups and presenting one URL to a build · Upstream authentication, proxies and TLS trust for remote repositories · Deploying artifacts: the deploy plugin, the upload interface and REST
Archiva's authentication and authorisation layer. Users and roles, the repository-scoped permission model that separates observers from managers, guest access and what anonymous read really exposes, and wiring it to a corporate directory.
Topics: Redback concepts: users, roles, permissions, resources · Repository observer and repository manager roles, and per-repository scoping · Global roles, the system administrator and least-privilege configuration · Guest access, anonymous read and locking down write · LDAP and Active Directory integration and role mapping · Deployment credentials for CI, and keeping them out of build files · Password policy, account lifecycle and the audit log
The background machinery that makes a repository more than a directory of files. The repository scanner and the consumers it feeds, index construction and search behaviour, metadata generation, and how to detect and repair the situation where the index no longer reflects what is on disk.
Topics: The repository scanner: schedule, full scan versus incremental · Known content consumers and what each one produces · Invalid content consumers and detecting artifacts that do not belong · Index construction and search behaviour, including artifact and class search · Maven metadata generation and snapshot version resolution · Metadata store backends and their operational differences · Repairing a stale or corrupted index · Browse, dependency and dependency-tree views as diagnostic tools
The client side, which is where adoption succeeds or fails. Maven settings and mirror configuration, distributionManagement for deployment, the same for Gradle and Ivy, and making CI agents resolve and publish through Archiva without credentials leaking into repositories.
Topics: Maven settings.xml: mirrors, mirrorOf patterns, servers and profiles · distributionManagement and deploying releases versus snapshots · Forcing all resolution through the repository manager, including plugin repositories · Gradle repository and publishing configuration against Archiva · Ivy and Ant-based builds · CI integration: credentials, agent configuration and shared settings files · Release promotion between staging and release repositories · Diagnosing resolution failures from the client side
Keeping the server alive. Snapshot purge and retention tuned to real volumes, backup and restore that has actually been tested, upgrade procedure, monitoring the things that fail first, and automating administration through the REST API.
Topics: Purge rules: retention count, days older, and choosing values that fit your snapshot rate · Disk growth modelling and capacity planning · What must be backed up: repository storage, configuration, database, index · Restore testing and recovery time · Upgrade procedure and rollback · Monitoring: JVM, disk, scanner duration, response times, upstream availability · The Archiva REST services and scripted administration · Common production failures and their signatures
The module most repository manager courses omit. What to do when Archiva no longer fits — because the estate went polyglot, because high availability became a requirement, or because component intelligence is now mandated — and how to move without stopping every build in the organisation.
Topics: Signals that you have outgrown Archiva · Format gaps: Docker, npm, PyPI, NuGet, Helm and what filling them costs · High availability, replication and multi-site distribution · Component intelligence and policy enforcement expectations · Migrating repository content to Nexus or Artifactory · Cutover strategy: dual-write, redirect, and client reconfiguration at scale · Preserving history, checksums and the audit trail through a migration · Migrating into Archiva from a file-share or ad-hoc repository
We rebuild the agenda around the tools you actually run.
Request a custom agendaDeploy Archiva with configuration and data separated from the installation, TLS terminated in front, and prove an upgrade is non-destructive.
Configure remote repositories and proxy connectors, warm the cache with a full build, then disconnect the upstream and prove the build still resolves.
Wire Redback to a directory server, map groups to repository-scoped roles, and create a CI identity that can publish to one repository and nothing else.
Reconfigure Maven and Gradle builds so every dependency, plugin and publication passes through Archiva, then verify with network-level evidence.
Tune purge rules against a realistic snapshot volume, then destroy the instance and rebuild it from backup while timing the recovery.
Plan and rehearse a migration to another repository manager: content transfer, checksum verification, client cutover sequence and a rollback point.
Billed yearly at ₹9,996
Max 8 to 10 hours of live instruction
Full program, private instructor
8–30 engineers · custom agenda · onsite or online · PO and GST invoicing
Refunds. If we cancel or postpone a cohort, you get a full refund within 15 days. There is no money-back guarantee otherwise.
Terms. Course material remains licensed to the attendee. Read the terms.
Your data. We don't share it with third parties. Privacy policy.
Certificate of completion
Good discussion, helped us to understand different tools in SRE.
Got good lab sessions which kept the new DevOps tool learnings to the point and it helped a lot in my career.
I took Terraform training with the tutor named Mithilesh. I requested to tailor the course curriculum for my needs. He did an excellent job of showing me how to write the Terraform script per the instructions provided.
My experience with the AIOps training was positive. The course covered important topics in a structured way, and Rajesh Kumar explained the concepts patiently. I found the practical aspects particularly helpful because they made the technical content easier to understand.
I was looking to improve my understanding of AIOps, and this training helped me achieve that goal. Rajesh Kumar explained the subject in a structured and practical manner. The sessions on different AIOps concepts were informative.
I recently did a SRE Session with Rajesh Kumar from DevOps School and the session was great. Right from 1st day till day 15, we had a very interactive session. Rajesh clarified our doubts and the tool demos were excellent without any hiccups. He simplified the concepts while sticking to the content with a fine balance between theory and practice. Am convinced he is one of the best trainers for SRE & DevOps concepts.
| What matters | YouTube + blogs | Generic online course | Freelance marketplace | DevOpsSchool |
|---|---|---|---|---|
| Named practitioner | No | Rarely | Varies per booking | Yes — same trainer each time |
| Production experience | Unknown | Unknown | Unverified | 20 years, named employers |
| Custom agenda | No | No | Sometimes | Built from your stack |
| Onsite delivery | No | No | Sometimes | Yes |
| Lab environment | None | Sandbox that expires | Varies | Your own cloud — skill goes with you |
| Assessment | None | Quiz | Rarely | Assignments + capstone per module |
| Per-attendee certificates | No | Sometimes | Rarely | Yes |
| Corporate invoicing | No | Limited | Varies | PO and GST |
| Post-training support | None | Forum, time-limited | None | Lifetime forum access |
Tell us the team, the stack and the timeline. You'll get a straight answer, not a sales sequence.
Talk to an advisorPrefer to call or email?
More ways to reach us on the contact page.