Consulting Services

Scope

• Pre-Assessment / Discovery Phase
• Migration Questionnaire for Pre-Assessment
• Assessment of source database to check compatibility for EDB/PGSQL
• Recommendations about databases which is the perfect candidate to start
• Detailed Analysis of incompatibilities objects like stored procedures, Functions, Packages, Views etc.
• Guidance to make incompatible objects to compatible to EDB/PGSQL

Out of Scope

• Hands on machine
• Installation and configuration
• Hands on application code modification

Prerequisites

• Structural backup of Oracle schemas which needs to migrate
• Access to application team and DBA team point of contact to assist Ashnik during the services engagement
• Migration Questionnaire answers

Deliverable

• Detailed migration assessment report with detailed object level analysis
• Effort estimation: Based on the above report, we will give you a detailed effort estimation with clear
• Recommendation of right migration strategy

Time Estimate

• Maximum allowable: Five(5) business days

Scope

• Review current CI/CD pipeline across build, test, deploy and monitor
• Access current capabilities and level of maturity for automation
• Analyse areas for improvement to expedite software development lifecycle
• Assist in recommendation to enhance monitoring of infrastructure and gain better visibility on microservices
• Review security and compliance across container development and deployment lifecycle

Out of Scope

• Configuration of current CI/CD tools sets
• Integration of CI/CD toolsets with other components not related to DevOps
• Investigation of CI/CD pipeline breakdown
• Performance testing of toolsets

Prerequisites

• Documentation of current CI/CD processes and architecture
• Provide details on current CI/CD toolset and version used
• Provide details on observations/challenges in current CI/CD pipeline
• Sample application with full CI/CD pipeline

Deliverable

• Documentation in PDF for recommendations and best practise on areas as covered in the scope
• Half-day session on sharing of observation, best practises and recommendation for DevOps

Scope

• A clear analysis of the decision boundaries based on standard enterprise patterns of Microservices
• Design of a Microservices approach for one application. This design would be provided as a series of documents and diagrams, details follow:
  • Context View – The overall understanding of the system at the enterprise level. This macro view allows one to see the various functions and practices in the whole initiative. This view is a bird’s eye view of the system design.
  • Container View – Describes the ‘containers’ the final system is deployed as. This relates specific technologies being implemented in a given context, how they relate to each other. When the system is building a series of Microservices, this is the level that describes the micro-services and how they interact with each other. This view covers more detailed aspects of application design.
• Documentation around the non-functional requirements that emerge out of the decision boundary discovery.
• Technology recommendations around each of the decision areas

Out of Scope

• Hands-on decomposition of monolithic applications – the implementation
• Documentation of any feature sets or user stories – these must be provided by the product management or design teams
• The component and code views are ‘implementation’ views and are considered out-of-scope for the engagement
• Documentation of any form for the existing application
• Exchange or review of any dataset or information deemed confidential or sensitive by the engaging party

Prerequisites

• Scheduled meetings with the relevant points of contact as may be needed for appropriate discovery of needs and decision boundaries (per the details in the approach section above)
• Documentation around the decision boundaries, where available
• Existing monolithic application along with any available documentation
• Any potential user stories, especially business rules that must be kept in consideration when designing the new solution
• A documentation of the database (or databases) involved along with working sample data
• The sample data must be sanitized and any sensitive information must be appropriately masked or obfuscated while still maintaining the integrity of the schema
• Familiarity with Linux and open source tools such as NGINX, Docker, Mesos, etc

Deliverable

• All documentation converted to PDF and delivered as a ZIP file
• Half-day session on sharing of observations, best practises and recommendations for Microservices