If the developer is alone or a minority, the development will proceed without a DBA.
I have been designing and developing DB first, and this method is subject to ever-changing requirements I suddenly wondered if I could respond properly, so I didn't pay much attention to it
I was looking for a development methodology, OOP, and DDD, and I got a question.
If program design is done first, not DB design
I don't know how it goes.
What is the difference between designing a DB first and designing a program first?
Please answer anything that can solve related questions, such as what stage it will proceed.
Thank you.
oop ddd design
I'm giving you an opinion based on my experience.
Usually, we understand the current plan as much as possible, design the DB, and then design the program.
But in reality, the plan keeps changing. Best practice is to implement it before the plan changes.
!If the plan changes in the middle, determine whether it is possible due to changes in the DB and program depending on the progress and continue to judge with the members whether the schedule is acceptable for the increased schedule.
If you design programs in reverse order and design DBs, you are more likely to miss data, and in the worst case, you may have to change the platform or language to make it possible.
© 2024 OneMinuteCode. All rights reserved.