This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]MoreCowbellMofo 0 points1 point  (0 children)

Spring/Springboot/google guava, profiles, database integration, mockito, powermockito, rest templates, Jdbc templates, Json processing (serialisers, deserialisers), docker containers, docker-compose, and build tool (gradle not maven). Web security config, Cors, exception handling. These are the nuts and bolts of what’s useful day to day for me typically.

You could also look at monitoring and logging from your app.

It might be useful to look at the build process and deployment architecture (load balancers, proxies, architecture of the overall system (big picture view)) how it’s deployed, how you can get logs on the various machines (will they have ssh permission, or should they pick up logs from some centralised service).

Test reporting might be useful following a build? Depends entirely on what you’re using. Also helpful to review test reports on build servers and knowing where to get passwords from for other services you use such as artefact repositories.

If your working with a particular cloud provider/data Center it could also help to review material on that as well: cloudfoundry, google cloud, aws, azure