Private corporate batches delivered onsite across Bangalore, or live online in IST (UTC+5:30) — taught by a practitioner who runs Nexus 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 Nexus Repository as infrastructure the whole build estate depends on: hosted, proxy and group layout across Maven, npm, Docker, PyPI, NuGet and raw formats; proxy tuning, negative caching and routing rules so builds survive a bad day upstream; blob stores, soft deletion and the compact and cleanup tasks that actually reclaim space; and content selectors, realms and user tokens so CI authenticates as a machine rather than as a person. Sessions run against a live instance and include the failures — a group whose member order changes resolution, a full blob store, a Docker repository with no retention, and seeding a disconnected environment.
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 Nexus that means a trainer who has run it in production — Sonatype Nexus Repository for Bangalore build teams — proxy resilience, blob store economics, content selectors and offline distribution — 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.
Onsite delivery is at your own office. Nexus sessions in Bangalore commonly run in Koramangala and HSR Layout for product teams, and along the Outer Ring Road, in Whitefield or Electronic City for platform groups, one site per day so cross-city travel does not eat into lab time. You provide the room, a screen and network access; attendees run their own Nexus instance in a container so repository, blob store and cleanup exercises are safe to perform, because those changes are disruptive on a shared server. Where the estate includes disconnected environments we build the offline seeding and export workflow in the lab so the pattern transfers directly. Sessions are scheduled in IST (UTC+5:30) and planned around release windows. Invoicing is in INR from our Indian entity with GST, against a purchase order where procurement requires one, and travel within Bangalore is included.
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 Nexus batchNexus Repository is Sonatype's repository manager, and the model it uses is small enough to hold in your head. Every format behaves the same way: a hosted repository for what you publish, a proxy repository that caches an upstream, and a group repository that presents several of them behind one URL a build can point at. Change one line in settings.xml, .npmrc, pip.conf or a Docker daemon configuration and every dependency now arrives through a server you operate, log and can take offline.
Underneath that uniform surface, Nexus separates components from storage. A component is the logical thing — a Maven artifact, an npm package, a Docker image — and it is made of assets, while the bytes themselves live in a blob store that can be a filesystem path or an object store such as S3. That separation is what makes the operational behaviour make sense: deleting a component marks its blobs for deletion but does not reclaim space until a compact task runs, which is why storage keeps growing for teams who delete things and never schedule maintenance.
The rest of the system is a set of levers most installations never touch. Cleanup policies and scheduled tasks bound growth by age, download date or version count. Routing rules stop a proxy from asking upstream for internal packages that will never be there. Content selectors express fine-grained privileges over paths and formats, so a team can be granted exactly one namespace. Security is a stack of pluggable realms — local, LDAP, SAML, Docker bearer token, npm token, NuGet API key and user tokens — mapped through privileges into roles. And a repository health check reports what is coming in from upstream, which is where component governance usually begins.
Build reliability became a measurable cost. Every failed build caused by a public registry outage, a rate limit or a slow international link is paid for in engineer time, and the fix has been well understood for years — put a caching repository manager in front of everything — yet a large number of teams still resolve dependencies directly from the internet on every build. Once they stop, the repository manager becomes a piece of infrastructure whose availability, performance and storage are somebody's responsibility.
That responsibility has grown. Software supply chain expectations mean an organisation is now asked what components entered its builds, from where, under which licences, and whether a specific artifact in production came from a pipeline or from someone's laptop. A repository manager answers all of those, but only if repositories are laid out deliberately, publishing is restricted, and anonymous deployment was never enabled.
Storage is the third pressure and the most predictable. Blob stores grow, Docker repositories grow faster, snapshot builds accumulate, and nothing is reclaimed without scheduled tasks and cleanup policies. The engineers in demand are the ones who can lay out repositories that survive reorganisation, keep the proxy layer resilient when the internet is not, model access with content selectors instead of shared accounts, and keep the storage line flat — and who can compare Nexus with the alternatives honestly when a migration is proposed rather than assumed.
What Nexus is made of and where the bytes go. The component and asset model, blob stores on filesystem or object storage, the internal database, deployment shapes and sizing — and the separation that explains why deleting things does not immediately free space.
Topics: Components, assets and repository metadata · Blob stores: filesystem, object storage and blob store groups · Soft deletion and the compact blob store task · Installation layout, data directory and configuration · Sizing from build volume and artifact churn · Editions and what the open-source version does and does not include
The three shapes applied everywhere. Hosted, proxy and group repositories for Maven, npm, Docker, PyPI, NuGet, Go, Helm and raw; group member ordering and its effect on resolution; release versus snapshot separation; and a naming convention that survives reorganisation.
Topics: Hosted, proxy and group repositories and how resolution flows · Group member order and resolution surprises · Maven release, snapshot and version policies · Docker repositories, ports, connectors and the registry API path · npm, PyPI, NuGet, Go and Helm specifics · Raw repositories for toolchains and large binaries · Naming conventions and repository lifecycle
Making every build resolve through Nexus. Maven settings and mirrors, Gradle repository configuration and init scripts, npm and pip configuration, Docker daemon and registry credentials, and enforcing that nothing quietly resolves from the public internet.
Topics: Maven settings.xml, mirrors and server credentials · Gradle repositories, init scripts and enforced resolution · npm registry configuration and scoped registries · pip index URL, trusted hosts and certificate handling · Docker login, credential helpers and insecure registry pitfalls · NuGet and Go module proxy configuration · Detecting builds that bypass the repository manager
The reason most teams install Nexus. Remote storage settings, connection and retry behaviour, metadata and negative caching, routing rules to stop pointless upstream lookups, authentication to upstream registries, and how the system behaves when the internet is unavailable.
Topics: Remote storage configuration, timeouts and retries · Metadata max age, not-found cache and cache invalidation · Routing rules and blocking wasteful upstream requests · Authenticated and proxied upstreams behind a corporate proxy · Rate limits and how caching removes them · Online and offline repository modes · Diagnosing a proxy that returns stale or missing content
Who may read, deploy and delete. Realms and their order, users, roles and privileges, content selectors for path- and format-level control, user tokens for CI, anonymous access and what it quietly permits, and auditing deployments.
Topics: Authentication realms and evaluation order · Users, roles, privileges and role nesting · Content selectors and selector-based privileges · User tokens and machine authentication for CI · LDAP and SAML integration · Anonymous access, deployment policies and redeploy rules · Audit logging and tracing who published what
Keeping the disk from filling on a Friday. Cleanup policies by age, last download and version count; scheduled tasks including compact blob store, rebuild index and purge unused; Docker retention specifics; and reporting growth to whoever owns the budget.
Topics: Cleanup policies and their criteria · Applying policies safely to a live repository · Scheduled tasks: compact, rebuild index, purge, repair · Docker image retention and untagged manifests · Snapshot retention for Maven and equivalents elsewhere · Measuring reclaimed space and monitoring growth · Alerting before the blob store fills
Nexus inside the delivery process. Publishing from Jenkins, GitHub Actions or GitLab CI; separating snapshot and release flows; promotion between repositories; then the disconnected case — seeding an offline instance, exporting and importing content, and governing what is allowed in.
Topics: Publishing from CI with scoped credentials · Snapshot versus release repositories and promotion · Staging and approval before a component becomes available · Seeding an instance for a disconnected environment · Exporting, transferring and importing repository content · Governing new components entering a restricted estate · Repository health check and component intelligence
Running it for years. Backup and verified restore, upgrade and rollback planning, high availability options, performance tuning and JVM sizing, log analysis and incident triage — then an honest feature and cost comparison with Artifactory and a migration plan in either direction.
Topics: Backup strategy for database and blob stores, and testing a restore · Upgrade planning, version compatibility and rollback · Availability options and their real constraints · JVM sizing, connection pools and performance tuning · Reading request and outbound logs during an incident · Common failures: full disk, stale metadata, auth loops, slow resolution · Nexus and Artifactory compared feature by feature · Migration planning in either direction
We rebuild the agenda around the tools you actually run.
Request a custom agendaBuild hosted, proxy and group repositories for Maven, npm, Docker and PyPI, then point real clients at the group URLs and verify every resolution goes through Nexus.
Warm the proxy caches, cut outbound access, and prove builds still complete — then add routing rules and negative caching so the failure modes are explicit.
Use content selectors and roles to grant write access to exactly one namespace, issue a user token for CI, and prove every other path is denied.
Apply cleanup policies to a bloated repository, handle untagged Docker manifests, run compaction, and measure the space actually reclaimed against the space deleted.
Assemble an approved dependency set, export it, import it into an isolated instance, and complete a real build inside the disconnected environment.
Back up a loaded instance including blob stores, destroy it, restore into a clean host, and verify components, permissions, tasks and scheduled policies survived.
Nexus is the repository manager Bangalore teams reach for when the budget is theirs to defend. Product companies in Koramangala, HSR Layout and Indiranagar, and mid-size engineering groups along the Outer Ring Road, standardise on it because the open-source edition covers hosted, proxy and group repositories across every format they use, and the first real question is operational rather than commercial: how to keep builds working when a public registry is slow, rate-limited or blocked by a corporate proxy. Proxying npm, PyPI, Maven Central, Docker Hub and Go modules through one server they control is the change that most visibly reduces failed builds, and it is usually the reason the training is booked.
The second Bangalore pattern is offline and restricted distribution. Aerospace, defence, space and semiconductor engineering here run build environments that are deliberately disconnected, and a Nexus instance seeded with approved components and moved inside is often the only supported way dependencies get in at all — which makes content selectors, routing rules, staged approval of new components and repository export the important part of the syllabus rather than a footnote. Running alongside both is a storage problem that arrives about eighteen months after installation: blob stores that grow without cleanup tasks, deleted components that are only soft-deleted until compaction runs, and Docker repositories nobody has ever applied a retention rule to. Bangalore job specs rarely say Nexus outright, but build, release and developer-productivity roles here assume the holder can keep a repository manager fast, bounded and available, and can compare it honestly against Artifactory when a migration is proposed.
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
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.
The Rundeck developer session was excellent and highly engaging. I appreciated how well the session was structured, with the theoretical concepts explained clearly and in simple terms. What stood out most to me was the demo — it was both informative and enjoyable. I especially liked how Rajesh walked us through not only the happy path but also the sad path, showcasing common issues and sharing practical troubleshooting tips.
| 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.