But there is a lot of difference between test and prod and if you have not coded taking prod environment in mind most likely code will fail in prod or result in exceptions.
So what makes the production environment different than development environment?
Here are a few things which I noted:
1) Production is all about the load/traffic/amount which will expose concurrency issues, load issues, memory, and CPU issues.
2) You will get a lot many scenarios in production that you might have thought of in development. I think through the process is not applied than most likely those scenario has not handled in production.
3) Different data input or incorrect data, one of the classic problems in production is the data that gets input to your program, be it from the upstream system or any other place you will get all sort of data and if your program doesn’t handle those very likely it will suffer.
4) Boundary conditions, this is somewhat related to above point data and scenarios but most of the boundary condition e.g. null, empty, etc exposed in production.
So if a code is written all these things and potentially domain-specific things and can sustain the test of production than it called a production-quality code and believe me it takes a lot of experience, skill and thinks through the process to write production-quality code not just in first time even after two or three iterations.
Though, as a developer, we should always strive for writing production-quality code in the first attempt.
6 Tips to Write Production Quality Code
Now let’s see how we can do that, what are the things we should keep in mind:
1) Get your requirements right, understand the problem, talk to the user or business person as much as possible this will help you to find different scenarios as early as possible. Many times business or user does not tell you everything it’s not their fault but it doesn’t come in mind right through.
So if you are frequently speaking, discussing, and presenting a solution to the most likely they will ask questions, give feedback which eventually exposes more scenarios and subtle details. Here experience plays an important role. More experience or domain knowledge you, much better code you will write.
2) Think through, Think through, and Think through. There is no substitute for this, it is more of a skill and art than science but you will get hold of this when you get more experience. For example, if a user says that you need replay capability in your program.
You should be able to think of all possible scenarios where you need to replay and what could be required for that, what would be a side effect of that. Does replay would be requested, what if the requesting system went down again, will you be able to re replay, etc.
3) Boundary condition, always think that you will get bad input, you will get null or empty, small or very large numbers, the function may get called at the wrong time, etc. you can get rid of this by writing the unit test for each boundary condition.
4) Concurrency, this is is the major culprit and big problem which exposes itself in production when due to load multiple threads get triggered and access your program concurrently. With the high-speed low latency electronic trading system and with many other java systems where its requirement to have a concurrent application this can only be addressed by proper design, if you get the design right you will safe otherwise you will need to bear the pain of redesigning or rewriting code. You can also expose concurrency issues by doing load testing in early QA cycles.
5) Exception handling, this is the by far most important characteristic of production quality code, it must be able to handle an exceptional scenario in a clear cut predefined way. The whole program should never be crashed due to one single bad input or scenario.
Here is also a nice diagram to remember these tips:
Thank you.
Related Java Tutorials
