Cloud Core

Introduction

© 2020 NetCracker Technology Corporation.

NETCRACKER CONFIDENTIAL AND PROPRIETARY. This document contains proprietary and confidential information that may not be reproduced or
disclosed to individuals that do not have a need to know. Disclose and distribute solely to those individuals that have a need to know.
1
 Netcracker Teams Structure L1 : Business Practices

Applied Business Practices implements and

delivers solutions that directly serve customer's
needs:
<<Business Practice>> <<Business Practice>> <<Business Practice>> • Portals, mobile applications
BSS OSS Billing • Billing and rating
• CRM and sales management
͞How to sell͟ ͞How to make͟ ͞How to charge͟ • Service provisioning and Order Management
• Network rollout and inventory

Platform implements common services that are

<<Business Practice>> not directly related to any business applications
but used them:

Platform • PaaS layer (kubernetes, data based and

queues)
• SDK – libraries and common microservices
͞Give SDK, Rules and Services͟ • Reporting and BigData
• Security – authentication, authorization
• Operational services – monitoring, logging
• DevOps
• Integrations Framework

2
 Application Logical Architecture
Clients: browser, mobile application, external Consumers
integration
layer Cloud Core Artifacts

Microservices that distributes frontend

Frontend Other Platform Artifacts
applications. Typically – nginx containers with Applied CDN
JS (Angular, React) layer Frontend Applied Applied
Microservice frontend frontend
Non-platform Artifacts
Service mesh that organizes cross-
microservice communication within cloud and Request Egress
Public gateway
communication between cloud and clients. Routing Layer Gateway

GraphQL Applied Backend

Identity Microservice
Authentication and authorization. Both for user Provider
Server platform libs
Façade Façade
requests and M2M Security Layer gateway gateway Access
Control
Applied Code
Security
Business microservices their self. Microservice
is implemented on top of SDK : base docker
Applied and Clinent platform libs
Applied Applied
image , framework (Spring, Quarkus), NC set common Backend Backend
Framework
Smartplug
of libraries. services Microservice Microservice Base image

Metamodel
Centralized access to any shared service XaaS Key-
DBaaS MaaS
(Data Base, Message Queue) manager
Configuration
management
Mostly- persistence layer- Data Bases,
Message Queues, complex 3 rd party services Infrastructure Vault Extensions
Database Queue

3
 Solution deployment architecture
Solution is composed from
Applications. Every application is a
namespace kubernetes group of pre-integrated microservices
OSS BSS Billing Deployer that are delivered and deployed
application
Business Business Business together. In NC we deploy in cloud
Persistent only applications, not individual
Application Application Application
volume(s) microservices.
Business Business Business
virtual machine
Application Application Application Applications are deployed to
Legend Cloud Core Cloud Core Cloud Core
namespaces. Typical deployment
architecture:
• Every Data Base and Queue has
a dedicated namespace. They
DBaaS MaaS Zookeeper could be used by several
Repository business applications at a time.
Consul
PG MongoDB Kafka RabbitMQ • DevOps tools (deployer) also has
Vault a dedicated namespace
Monitoring Cassandra OpenSearch • Business applications- multiple
ArangoDB Redis applications are deployed no one
namespace. Cloud Core is pre-
Logging Data Bases Message Queues Registries installed to this namespace.
• Monitoring, Logging and
Infrastructure
Repository are usually deployed
on VMs

4
 Netcracker Teams Structure L2 : Platform
Cloud Core provides common SDK (set of Platform Services are teams that provides service instead of a product.
common microservices and libraries) for Service means some working asset like devops tools, consultancy and
microservice implementation. SDK covers ideology such as Security or professional services such as Cloud
major non-functional aspects – security, cross- Operations
microservice communication, DB and queue
allocation etc. Also implements tools used on
devops area.
The BIG Platform
The SMALL Platform Platform Applications Platform Services

Integrations Platform DevOps

Cloud Core
Workplace Platform Security

Infrastructure platform provides Infrastructure Data Management CSE

kubernetes , data bases, message Platform
queues and similar distributives by
“netcrackerifying” and “cloudifying” 3rd BigData and ML Cloud Operations
party distributives such as Cassandra,
Kafka etc.

Platform Applications provides several technical domains such as

Reporting and BigData , ML, Integrations, UI frameworks.

5
Netcracker Teams Structure L3 : Cloud Core
Cloud Core
Lead (Alexey Efimov)
E2E Architect (Konstantin Bulanov)
TM (Yury Nikitenko) TM (Alexey Prokofiev)

Framework Application Security Extensions Toolset

Service Mesh Security lead Lead Builder
Nikita Sirotin Alexander Agishev
DBaaS and SDK Security Architect Backend Deployer
Andrey Dryakhlov
MaaS Identity Mgmt Frontend CMDB+ Cockpit

Backup and DR Access Control Delivery Gateway

Common Common Common Common

6
Work principles
1. Application developer should receive a platform for free
2. Distributed Team
3. Automated Quality Assurance
4. Attention to backward compatibility
5. Agile process with 4-week sprints
6. Daily syncups within a team and between leads

7
 Process overview

05.Sept
18.Aug
01.July

01.Oct
E2E Release
22-2 22-4
22-3
E2E Release Development Stabilization

Developmen Stabi
Development Development Development
Core Services Sprint Sprint Sprint
t lizati
Sprint on

Libs
development

8
 Main Resources
• Bass Space : https://bass.netcracker.com/display/CLOUDCORE/Cloud+Core+Home
• Trainings: https://bass.netcracker.com/display/CLOUDCORE/Development+Trainings
• Core Architecture: https://bass.netcracker.com/display/CLOUDCORE/Cloud+Core+architecture
• Key processes : https://bass.netcracker.com/display/CLOUDCORE/Processes+and+regulations
• Template microservices: https://
bass.netcracker.com/display/CLOUDCORE/Stable+Versions+Registry#StableVersionsRegistry-Samplemicroservices
• Spring SDK libraries: https://bass.netcracker.com/display/CLOUDCORE/Spring+Cloud-Core+libraries
• Go SDK libraries: https://bass.netcracker.com/display/CLOUDCORE/Golang+Cloud-Core+libraries
• Quarkus SDK libraries: https://bass.netcracker.com/display/CLOUDCORE/Quarkus+Cloud-Core+extensions
• Blog (videos in Russian, presentations- in English): https://bass.netcracker.com/pages/viewpage.action?pageId=706398687
• Requirements JIRA : https://psup.netcracker.com/browse/PDSDNREQ
• Support JIRA : https://psup.netcracker.com/projects/PSUPCLFRM
• Development JIRA : https://
psup.netcracker.com/secure/RapidBoard.jspa?rapidView=1187&projectKey=PDCLFRM&view=planning&issueLimit=100
• Git group : https://git.netcracker.com/PROD.Platform.Cloud_Core