4 ms·

I am seriously glad I don't work on this project!

• bob1029 7y ago
  Care to elaborate on which aspect noted above is adverse from your perspective? I would be happy to provide more context and explain in more detail some of the reasoning involved in our decisions.
  • hdfbdtbcdg 7y ago
    > Deserializing a JSON blob to/from a column into/from a model containing 1000+ properties in complex nested hierarchies > complex, rapidly-shifting business models Your business logic classes have 1000+ properties. And you plan to not migrate them when the schema changes but leave many instances with old versions of the schema sitting in the datastore. Your application logic is going to get nasty!
    • bob1029 7y ago
      The other aspect here is that the lifetime of these objects is very brief for our application. Typically 10-60 minutes. Schema changes, while breaking, are tolerable along business cycle boundaries.
      • hdfbdtbcdg 7y ago
        Why use SQL at all? It sounds like you needed a key value store?