Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I have heard a comment that using a DDL script for a database installation is anti-agile. Is this true and if so why? I have been looking online for my answers but couldn't find anything.
Thanks
I don't know your exact context, but I would say that DDL is very pro-agile as it supports a repeatable installation process. Maybe they meant that designing the entire database prior to development is anti-agile. I would tend to agree with this assessment, but there is nothing inherently anti-agile about DDL.
Hope that helps!
Brandon
Supporting incremental updates is more convenient and also allows for repeatable builds.
This allows the database to be "refactored" or "evolve" - as changes to it are seen as a series of small adjustments to a base schema.
This allows for constant upgrades without having to manage database versioning explicitly yourself. The database is the source of its own version and the upgrade process only applies appropriate deltas if they are required.
There are several tools that can help with this - the best know being probably ruby on rails active record migrations. For java environments then dbdeploy is pretty good (I think there are versions of dbdeploy for .net and php environments too).
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I have a legacy Ruby on Rails API project, I notice that the project uses both active_model_serializer and Jbuilder. There are app/serializers diretory for active_model_serializer, and app/view/api/ for Jbuilder.
I'm new to Ruby on Rails API. From what I have read from the internet it seems active_model_serializer and Jbuilder are both used to deal with JSON data, there's even an article arguing which one is better.
I don't know which one is better, but is it a good practice to use both?
There's no problem in using both, but it's definitely not a good practice. It can be confusing for new people coming to the project. I'd say it's ok to use both if you transition from one to the other (most often from Jbuilder to AMS), but it's good to eventually stick with one of them.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
Is there any rationale why HapiJS endorses using 4-space indentations?
Source: http://hapijs.com/styleguide
Short answer: No better reason than anyone else - styleguides are typically only rules for project maintainers. They had to adopt some convention and that was the choice. As a user, you don't really need to care.
Long answer: Hapi is a great framework, built by the folks at Walmart. and specifically a person named Eran Hammer who was unhappy about some architectural choices made by Express, another server framework for Node. It is somewhat opinionated in general, it was effectively created in an environment of opinion, not to mention a large company (which means it desperately needed a convention). That said, you can safely use the Hapi API with any indentation you want, including tabs, though. Likewise, the Hapi internals could have been written the same way. Their specific choice likely comes down to established tools or conventions already in use at the company. Many different projects make different choices for a variety of reasons. In my experience, many large JavaScript applications go with 2 spaces and the Node.js core itself is written with 2. But there's nothing wrong with those that do otherwise.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
I am creating an application where each user will have his own workspace which will consist of some text files. He will be editing and saving these files excessively.
I want to implement a version control system for each user to keep track of his work and revert back and forth to any previous version if he wants to.
I would also like users be able to fork into each others workspace to copy the content to their own workspace just like in plnkr.co, make changes and commit easily.
My stack is node.js and angular.js
Where should I start, to implement it. I guess there should some way to use git or some other open source project. Does anybody have any idea what plunker is using?
Super late response, but for anyone stumbling across this, try checking out git=annex
We used this at one of my old jobs for keeping track of fMRI datasets. It's best used for large data though, so one may want to find something similar but perhaps better aligned for what they need.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
Can you give several indications (pro and cons) concerning the fact to put the menus of a web application inside the database?
Mainly it depends upon your requirement of your application. Its not always a good approach to bring a drill machine to make hole in sand. Every approach has some limitations and need more efforts if you do apply some alternate approaches.
In cons you can consider
Performance ( to prepare dynamic menu every time you load the master page also the static text less time to process in compare to dynamic)
Configuration will be always an issue while adding or modifying the menu
(Always need a database guy at the time of any change)
Pros
Highly configurable and completely dynamic
Can add/remove the attribute and change the text without affecting anything in code.
We have some solutions also to overcome from the cons
In case of performance we can use caching but everytime the menu change you need to recycle the application pool.
For configuration you can provide a page to control the menu content. (No Sql guy needed)
So as I said earlier you can go either way as your application adopt easily and in much better way.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
My aim is to build an aggregrator of news feeds and blog feeds so as to make
searching/tracking of entitites in it easy. I have been looking at many solutions out there like Terrier, Lucene, SWISH-E, etc.
Basically, I could find only 2 sources of comparison studies done on these engines and one of them is kinda outdated. Basically I want a search engine which would be used in a case in which the data size is not too large, but the indexing will be frequent, every 30 minutes or so. I feel Terrier is not a good tool to be used in this case. It works better when the data size is large and updation frequency is low. Can somebody who has worked in the Information Retrieval field offer some advice ?
Lucene is well known and supported, so personally, that would be my first choice.
If you find a ready-to-use search engine, check out fastcatsearch.
It has been developed for commercial search, and applied to a lot of various sites.
Faster than lucene, and has web-based web manager to use easily.
Hosted in github, and check it out. https://github.com/fastcatgroup/fastcatsearch