Platform Build and Development

With Call It expected to be a high traffic application that needs to be built to change
instead of built to last, the micro-services architecture is of choice with its tangible
benefits including an increase in scalability, flexibility, agility, and other significant
advantages. The entire functionality is split up into independently deployable
modules which communicate with each other through defined methods. Each
service covers its own scope and can be updated, deployed, and scaled
independently.

BizDevOps approach including automation and event monitoring at all steps of the
software while factoring in the business drivers will be employed to shorten the
systems development life cycle. Features, fixes, and updates delivery will be
frequent and in close alignment with business objectives.

General Architecture

N is total number of micro services; each micro service has a defined business
functionality which is a small entity by itself.
Examples:
Server 1 : API (Gin GoLang / Rails 5/ Nodejs with Koa/sails)
 Server 2 : DB (Mongodb/ Firebase)
Server 3 : API (Rails 5/ Nodejs with Koa/sails)
Server 4 : DB (Mongodb/ Firebase)
Server 5 : UI Server – Angular / React
Server 6 : Chat server
Server 7 : Reporting/Analysis

Originally envisioned as below, the technology platform can be tuned per the
preferences at the time of development

Initial Launch (minimum viable product)

We believe that the MVP is not just a product with some perceived frills left out of the development
cycle, or a way to get the product out the door a little faster. It is a process that we expect to repeat
over and over again: Identify the riskiest assumption, find the smallest possible experiment to test
that assumption, and use the results of the experiment to course correct.

The Call It application, like any other, has many assumptions. We assume that we have an idea about
what the users are looking for, how the design should work, what marketing strategy to use, what
architecture will work most efficiently, which monetization strategy will make it sustainable, and
which laws and regulations we have to comply with. We are aware that some of our assumptions
will be wrong. The problem is, we don’t know which ones.

To this end, the MVP is to have an initial website that allows

1) User logins
2) User profile management
3) User review posting based on
a. Service Provider Sector
b. Service Provider
c. Service Ratings
d. Text review
e. Picture / video
 Rollout Time Table

    Week
1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 3 3 3 3 3 3
  1 2 3 4 5 6 7 8 9 36
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
Define Specifications                                                                        
Overall Architecture                                                                        
Project Planning                                                                        
Assemble Team                                                                        
Wireframes /
                                                                       
Design UX
UI                                                                        
MVP
                                                                       
Developmen development
t Product
                                                                       
Development
Test Plans                                                                        
Testing                                                                        
Testing & QA User
Documentatio                                                                        
n
Maintenance and operations

Head Task Outline

Operational Monitor, maintain, backup, log analysis, and recovery testing for the servers and
Support applications. Troubleshoot, operations, maintenance, administration, application, network,
migration, and database support.
Software Provide software engineering and maintenance services using the full system development life
Maintenance and cycle (SDLC).
Upgrades
Infrastructure Manage the entire applications infrastructure capability.
Management .
Services (IMS)
Configuration Conduct configuration management for the applications infrastructure capability including
Management servers, operating systems, vendor inventories, patching and upgrade services, as well as
software migration services.
Network/ Provide hardware technical support for servers; monitor performance of
Hardware installed applications and servers. Administer vendor changes/patches and conduct
Support performance tuning.
Resource Manage the network infrastructure resources.
Management
Backup and Implement and manage backup/archive strategies for systems and servers. Perform backup,
Recovery storage, and disaster recovery functions.
Management
Installation, Install, configure, and tune application services. Monitor system performance and coordinate
Configuration, tuning and performance solutions.
and Tuning .

IT O&M Planning Perform capacity planning analysis, and make new server recommendations, configuration
change recommendations, and financial recommendations for hardware/software
acquisitions.
Data management and security

The system will be secured across various dimensions to fit the goals for data
management systems like confidentiality, integrity, and availability. These can
be categorised in terms of general operational goals as well as technical
concepts as below

• Perimeter Access to the system secured from a variety of

internal and external network threats as well as a variety of
sources. Network isolation by proper configuration of
firewalls, routers, subnets, and the appropriate use of public
and private IP addresses. Authentication systems ensure that
people, processes, and applications identify themselves and
attest they are who they say they are, prior to gaining
access.
• Data is always protected from unauthorised access.
Communications between the nodes is protected. Encryption
ensures that contents exposed to/removed by unauthorised
actors are unusable, even if network packets are intercepted
or hard-disk drives are physically removed from the system.
• Access to any particular service or data item within the
system is specifically granted. Authorised users can only see
the data and use the processes to which they have been
granted specific access, after they have authenticated
themselves.
• Analysis System transparency with respect to the history of
data changes as well as capability of meeting data
governance policies is ensured. Auditing mechanisms make
certain that all data actions and its lineage—source, changes
over time, etc. are documented as they happen.

Data-at-rest (databases, data warehouses, spreadsheets, archives, tapes, off-site

backups, mobile devices and/or any other type of data store) and data-in-use, is
encrypted with fault-tolerant key management system. Auditing mechanisms are
to be set in place, that comply with specified and stipulated industry,
government, and regulatory standards, while extending from the Call It system
to the other systems that integrate with it.