I am thinking about setting up a project where a one-year development / built phase of a rest-API Server is planned. Providing an initial version in three months and deploying updates every month during the first year should be enough.
Further information to consider:
- After the services are built, they should be relatively stable for a long time. It is not expected to change the code every week. Probably one time in three months.
- There are only 10 people affected if the API does not work. And there will be no major business impact from being down.
- Code is not affected as a whole. Changes in one web service API will not affect others.
To set up a DevOps structure in order to ship updates fast and continuously is questionable since it takes some effort to set it up with no real benefit. Since there are not many changes expected during the lifecycle, there is no real benefit of DevOps.
Is this view right? what else should I consider?
A friend recommended me to use DevOps procedures anyway. Does this makes any sense?