« My 2 Cents on Lotusphere 2012 | Main| I will show you mine if you show me yours »

There is more than one way to skin a cat

Americans sometimes use a funny little expression: There's more than one way to skin a cat.

This is a (kind of creepy) way of saying that there are several different ways to accomplish a given task. And this is my challenge. My developer side says to do it one way, but my admin side might have a different perspective.  In the end, a decision must be made one way or the other. Case in point:

Recently, I completed the first part of a source code control and build process management implementation (FYI, Teamstudio knows quite a bit about source code control). The team included Chris Blatnick of Interface Matters fame, Kevin Petitt of SuperNTF fame, and Jamie Magee of Martin Scott and NoteMan Tools fame.  It really was special for me to be able to teach these guys anything.  

All of us are familiar with other tools, as well, like the ones from Ytria. The point here is that you can be so much more productive if you invest in some tools. Of course, we all prefer that you choose *our* tools, but what we really want is to help you deliver the best solutions for your users in the most cost effective way possible. At the risk of repeating myself, that generally means you need to invest in some tools.  (For what it's worth, I definitely like the 'free' ones, but you should always keep in mind that you get what you pay for).

Anyway, here's the challenge.  I came across an agent that created a document collection by doing a search.  My first reaction (from the developer side of my brain) was to just create and use a view.  Further review showed that the agent ran once a week and only took 20 seconds.  That's when my admin side took over, and said: Why have the server maintain the index for this view all week long, when it would only be used once a week?  

Any thoughts?  Is a search always bad?  How much overhead is noticeable when maintaining the view?  Multiply this by dozens of databases.  How would you decide?

Category

Comments

1 - That is a great point. I see it in domino all the time, in RDBMS development, queries are how people get data, but in Domino Development it appears that there may be 50 views and only 5 are used in the app as views that the user looks at. Its definitely a performance hog to have the view maintained that whole time for a look-up every once in a while.

2 - Good point you are rising. What I usually try to do is have a setup document where you can either specify a view (in the best case an existing view!) or a search formula. This way I am more flexible without having to change the database design. Additionally I can decide for an individual NSF if a view or search performs better.
In general I prefer the search as it provides a lot more flexibility. I have seen so many databases with lots of views where nobody has any idea which views are used and which not. It's hard to keep track of these views and maintaining these costs a lot of performance.

Cheers - Michael

PS: Yes, I have been to A. Pollack's session about Performance Programming... ;-)

3 - This is also affected by the number of documents in the database as well. When you are testing your agent in development with maybe a few hundred documents, you get much different results than running against a few thousand documents.

4 - I like this site.Thank you for the information that provided.

5 - Coach Outlet Online have already built a good brand image in customers' heart. You can always find a luxury Louis Vuitton Bags that can catch your heart, you will have the surprise when you place the order from { Link } Go head! We ship your order as soon as possible, top convenient for your business. Please feel free to buy them.

6 - Coach Outlet Online have already built a good brand image in customers' heart. You can always find a luxury Louis Vuitton Bags that can catch your heart, you will have the surprise when you place the order from { <a href="{ Link } rel="nofollow" target ="blank">Link</a> } Go head! We ship your order as soon as possible, top convenient for your business. Please feel free to buy them.

Post A Comment

Feeds

Custom Button Custom Button

Category Cloud

Disclaimer

The views expressed by the authors on this blog do not necessarily reflect the views of Teamstudio, those who link to this blog, or even the author’s mother, father, sister, brother, uncle, aunt, grandparents, cousins, step relations, any other blood relative - and sometimes not even the author himself or herself.

Comments on this website are the sole responsibility of their writers and it is assumed those writers will take full responsibility, liability, and blame for any libel or litigation that results from something written in, or as a direct result of something written in, a comment. The accuracy, completeness, veracity, honesty, exactitude, factuality and politeness of comments are not guaranteed. Oh, how they are SO not guaranteed.
en-us,en;q=0.5OFFCCBot/1.0 (+http://www.commoncrawl.org/bot.html)38.107.179.211getthemostfromnotes.comHTTP/1.180Lotus-Domino/tsblog.nsf/D6Plinks/KFRA-8R4M5G