Hot answers tagged

10

Store the words using a text format, and build a database during the build. Instead of storing the information in binary format and storing the binary file in the version control, keep the pairs in a CSV file. This allows you to easily change it, commit the changes and, later, diff the changes with ease. Later, when you actually need this data in a ...


3

If you donot like the additional constructor arguments for the dependencies you need a DI-Container to handle the instance creation for you. You can use either an existing di-container framework or implement a poor mans version on your own public PoorMansDiContainer : IPoorMansDiContainer { private IService mService = null; private IFooService ...


3

A different approach would obviously be to develop a more "componentized" application, where each business functionality is achieved through an independent module. Am I right in considering a layered architecture better, at least in containing the total cost of ownership and development of the application? If your "independent modules" or ...


3

Fowler is only referring to the mapping between the in memory representation of the document and the document itself, not the persistence of changes made to the representation. You would still need to separate the responsibility of persistence from the domain model. The key here is that you would have no mappings between those two responsibilities, so ...


3

I wouldn't say you're using bad design. There is always a cost in coding--to win the most 'CS class' worthy / most object-oriented award isn't really what coding is about. Code is a tool, just like any other and like most tools--you invent uses for those tools as needed. I find it easier myself to use a static class for 'utility' type stuff as you have ...


2

You use the naming conventions for convenience, and the configuration file for flexibility and explicitness. In the case of ASP.NET MVC, if you set up a sensible URL structure and get your names right, ASP.NET MVC will automagically wire up your routes and everything just works. However, if you need a special url formatted in such a way that does not ...


2

I think two issues to consider are: (and you're referenced this above) - do you need to find child nodes ? In which case you perhaps want to avoid storing sizeable hierarchies and instead store the individual Foos such that they're immediately searchable. That may impact tree construction/retrieval times Do you want to move children between trees? If you ...


2

Database systems can implement very different approaches. Just compare SQL vs. NoSQL. And for the latter compare key-value stores with graph databases. So you'll not find a silver bullet that will offer a single API with all the benefits of these databases. So you'll have to narrow down your scope. Considering the limits, filtering, ordering, many of ...


1

Your Input Database and your Output Database are each at Layer 1. Layer 2 will contain two Translators, one for each Database at Layer 1, that translates between the particular database objects and a "common" (or "universal") object type. Layer 3, your "application", manipulates the common objects. You could view this as a pipeline bent into a "U" shape.



Only top voted, non community-wiki answers of a minimum length are eligible