Software Development: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
 
(76 intermediate revisions by the same user not shown)
Line 1: Line 1:
=Cloud Service Delivery Models=
=Internal=


==External==
* [[Software Engineering]]


* NIST definition of Cloud Computing http://csrc.nist.gov/publications/nistpubs/800-145/SP800-145.pdf
=Overview=


==Infrastructure as a Service (IaaS)==
With any of the delivery modes below, the provider controls and manages some portion of the technology stack. The customer manages the portion of the technology stack that is not managed by the provider. The benefit is that the customer controls the design of its portion of the stack.


The IaaS delivery model lets the user of the service to provision processing, storage, networking and other computing resources on which they can run O/S and applications. The service users do not control the underlying computing infrastructure except select networking configuration or perhaps the physical location of the resources at gross geographical level. Infrastructure as a service is targeted at teams that are actually building out infrastructure.
Software development makes [[Software_Architecture#Overview|software architecture]] to materialize, and the set of rules and practices that go into software development belong under the larger umbrella of [[Software_Engineering#Software_Development|software engineering]].


Example: amazon web service, IBM cloud.
=A/B Deployments=


==Platform as a Service (PaaS)==
{{Internal|OpenShift_Application_Operations#A.2FB_Deployment|A/B deployment with OpenShift}}


"Platform as a Service" describes an additional level of services layered on top of an [[Software_Development#Infrastructure_as_a_Service_.28IaaS.29|infrastructure as a service]] foundation. These services include operating systems, database, middleware, etc. "Platform as a Service" are platforms for building and running custom applications, and are targeted at application development teams.
=Twelve-Factor Application=


Example: Google app engine.
{{Internal|12 Factor App|Twelve-Factor Application}}


External:
=Semantic Versioning=
{{Internal|Semantic Versioning|Semantic Versioning}}


* http://en.wikipedia.org/wiki/Platform_as_a_service
=Good Reads=
* Salesforce - What is PaaS? http://www.salesforce.com/paas/
* http://www.infoq.com/presentations/Java-in-the-Cloud-PaaS-Platform-in-Comparison
* Netflix Adrian Cockcroft on Architecture for the Cloud http://www.infoq.com/interviews/Adrian-Cockcroft-Netflix


==Software as a Service==
* https://www.joelonsoftware.com/2000/04/06/things-you-should-never-do-part-i/


=DevOps=
=Developing Applications for the Cloud=


A collaborative process enabled by automation where ''application development'', ''QA'' and ''Operations teams'' jointly accelerate delivery of new business application and services. DevOps emphasizes ''collaboration'' and ''cooperation''.
{{Internal|Developing Applications for the Cloud|Developing Applications for the Cloud}}


=CICD=
=Microservices=


==Continous Integration (CI)==
{{Internal|Microservices|Microservices}}


Continous Integration is a software development practice that involves the following:
=Infrastructure as Code (IaC)=
* Verifies build integrity by checking if the source code can be pulled from repository and built for deployment. The build process may include compilation, packaging and configuration.
* Runs and validates the unit tests: executes all unit tests created by developers and validates the test results. This step insures that the source code was not broken as a side effect of the commit.
* Runs and validates the integration tests.
* Identifies problems and alerts the teams.


In the DevOps culture, CI is mandatory, and it performed automatically by a tool that runs automation scripts to eliminate all human intervention during the CI process.
''Infrastructure as Code'' is an approach to IT systems infrastructure management, where various elements of the underlying hardware infrastructure are represented as programming constructs rather than physical hardware. This approach can be used in combination with automation tools to provide the ability to provision infrastructure in a repeatable and reliable manner.


The CI process requires a source code repository and a continuous integration server, that pulls code from the source repository and runs the build. Developers must check in as often as possible, every time a new piece of functionality that is verified by unit tests that pass is added. The build must be completely automated and must run without human intervention, and it must be fast.
=Code Review=


Testing - especially the integration testing - must be done in an environment that is as close to production as possible.
{{Internal|Code Review|Code Review}}


The CI process provides rapid feedback on the state of the project, each unit test or integration test-verified assertion that gets broken by a commit is immediately shared with the entire development team. The process is run every time there's a commit, presumably many times a day. Every member of the team must be able to easily access the build results.
=Simplicity=


The build process should generate software that can be deployed at any time - a good release candidate.
* https://thinkingsideways.net/code/2019/03/24/simplicity-over-flexibility.html
* https://www.infoq.com/articles/simplicity-manifesto-development


==Continous Deployment (CD)==
=Scrum=
 
* https://medium.com/@aevitas/the-tax-you-are-paying-for-using-scrum-50f12298b422
 
=Domain-Driven Design=
{{Internal|Domain-Driven Design|Domain-Driven Design}}
=Software Security=
{{Internal|Software Security|Software Security}}
=Consistency=
* https://medium.com/@jgefroh/why-consistency-is-one-of-the-top-indicators-of-good-code-352ba5d62020
 
=Software Development Practices=
* [[Continuous Delivery#Overview|Continuous Delivery]]
 
=To Process=
 
* Grady Booch - Building the Enchanted Land https://www.infoq.com/presentations/ai-best-practices. Health of the system: "do you have a regular process of release?" "do you have a sense of architecture?"
* [[Feature Toggle]]

Latest revision as of 23:14, 2 July 2023

Internal

Overview

With any of the delivery modes below, the provider controls and manages some portion of the technology stack. The customer manages the portion of the technology stack that is not managed by the provider. The benefit is that the customer controls the design of its portion of the stack.

Software development makes software architecture to materialize, and the set of rules and practices that go into software development belong under the larger umbrella of software engineering.

A/B Deployments

A/B deployment with OpenShift

Twelve-Factor Application

Twelve-Factor Application

Semantic Versioning

Semantic Versioning

Good Reads

Developing Applications for the Cloud

Developing Applications for the Cloud

Microservices

Microservices

Infrastructure as Code (IaC)

Infrastructure as Code is an approach to IT systems infrastructure management, where various elements of the underlying hardware infrastructure are represented as programming constructs rather than physical hardware. This approach can be used in combination with automation tools to provide the ability to provision infrastructure in a repeatable and reliable manner.

Code Review

Code Review

Simplicity

Scrum

Domain-Driven Design

Domain-Driven Design

Software Security

Software Security

Consistency

Software Development Practices

To Process

Retrieved from "https://kb.novaordis.com/index.php?title=Software_Development&oldid=97152"