Continuous Integration and Continuous Delivery
Order ID:89JHGSJE83839 Style:APA/MLA/Harvard/Chicago Pages:5-10 Instructions:
Continuous Integration and Continuous Delivery
Partner with Design/Architecture, development and Product team to design and drive the infrastructure needs of the product, with a strong focus on automation & operational best practices – 25%
- Design and improve new/existing software architecture in order to increase uptime of the systems resulting is cost saving and business efficiency. We will use HAproxy for this purpose.
- Design the systems to be easily scalable so that there won’t be any impact to the customers during high traffic sales season like Thanksgiving, Christmas etc. we will achieve this using MongoDb, PCF and HAproxy.
- Work closely with the developers and create a software infrastructure which is productive and efficient for developing and deploying code. We will use Docker and Jenkins for this task.
- Automate day-day infrastructure activities using Chef which will increase the uptime of the systems hence increasing end-user satisfaction.
Own, build & implement solutions across platforms to solve varieties of problems – 25%
- Software scalability is the biggest problem for enterprise software architecture. This is highly complex in nature and we need to achieve this keeping the existing business running as well as onboarding new technologies without any impact to the existing customers.
- Identify errors in the newly deployed code as quickly as possible is the need of the hour. We need to use strategies like high-availability, active-active datacenter model etc to keep business running and simultaneously resolve code errors in the production environment.
- Adhere to payment-industry standards is a must for all companies processing customer’s payment information like creditcard payments. This is called PCI standards. We achieve this by increasing the security of our software systems in all the layers/components like ssl-certificates, firewalls, application logs etc.
- Make software applications respond faster is very important to gain business and customers. Main ingredient to achieve this, is a strategy called caching. We make use of Akamai to achieve this.
Lead troubleshooting application components and recommend refactoring of applications to make them suitable for cloud native environment – 15%
- Troubleshoot is very critical in finding out the root cause for an error in the software systems. We identify this by using tools such as AppDynamics and Splunk.
- Move software systems to cloud have many benefits like efficiency, less expenses and ease of maintenance. Migrating existing legacy systems into cloud platforms is very tricky since existing business should not undergo any negative impact. Phased strategic migration of legacy systems into platforms like cloud foundry adds as a catalyst for migration into cloud.
- Develop scripts in shell and python to capture and troubleshoot errors immediately. Also making use of these scripts to pro-actively monitor software applications to mitigate any future problems.
Build and maintain end to end CI/CD pipelines and ops tool stack built on Jenkins, Chef, PCF etc. – 20%
- CICD (Continuous Integration and Continuous Delivery/Deployment) pipeline is needed to be setup for faster development and deployment of the code into production. The faster we can deploy the code, faster will be the availability of a new feature to the end customer.
- Build all the layers in CICD using Jenkins, bitbucket and artifactory.
- Develop and automate operational tool stack using Chef and PCF (pivotal cloud Foundry).
- Maintain CICD pipelines is required for a error-free, smooth code deployment. This is achieved by customizing Jenkins using shell scripts and Python and configuring Jenkins for timely alerts to our emails.
Work in an Agile environment with development and testing team to provide solutions from DevOps prospective – 15%
- Devops is a critical role bridging the gap between developers and operational team. Regular standups and clear communication across the teams is necessary to understand issues respective to the individual team and coming up with implementation plans.
- Solve Development issues by creating a stable infrastructure for code deployment and enhanced monitoring systems.
- Solve tickets in agile environment using efficient process like scrum and Kanban.
- Continuous Integration and Continuous Delivery
RUBRIC
Excellent Quality
95-100%
Introduction 45-41 points
The background and significance of the problem and a clear statement of the research purpose is provided. The search history is mentioned.
Literature Support
91-84 points
The background and significance of the problem and a clear statement of the research purpose is provided. The search history is mentioned.
Methodology
58-53 points
Content is well-organized with headings for each slide and bulleted lists to group related material as needed. Use of font, color, graphics, effects, etc. to enhance readability and presentation content is excellent. Length requirements of 10 slides/pages or less is met.
Average Score
50-85%
40-38 points
More depth/detail for the background and significance is needed, or the research detail is not clear. No search history information is provided.
83-76 points
Review of relevant theoretical literature is evident, but there is little integration of studies into concepts related to problem. Review is partially focused and organized. Supporting and opposing research are included. Summary of information presented is included. Conclusion may not contain a biblical integration.
52-49 points
Content is somewhat organized, but no structure is apparent. The use of font, color, graphics, effects, etc. is occasionally detracting to the presentation content. Length requirements may not be met.
Poor Quality
0-45%
37-1 points
The background and/or significance are missing. No search history information is provided.
75-1 points
Review of relevant theoretical literature is evident, but there is no integration of studies into concepts related to problem. Review is partially focused and organized. Supporting and opposing research are not included in the summary of information presented. Conclusion does not contain a biblical integration.
48-1 points
There is no clear or logical organizational structure. No logical sequence is apparent. The use of font, color, graphics, effects etc. is often detracting to the presentation content. Length requirements may not be met
You Can Also Place the Order at www.collegepaper.us/orders/ordernow or www.crucialessay.com/orders/ordernow Continuous Integration and Continuous Delivery