Skip to main content

Why not to use default solution for any type of project

By
In today post we will talk about how why is not a good thinks to use a ‘template’ solution/setup for any project.
Let’s imagine the following scenario. You need to develop an application that will require storing data to a repository. If it’s a big project, a group of architects or technical advisors (from company) will be called that will try to design an architecture for the application and identify the stacks/frameworks that will be used.
Usually a company that starts to use a specific framework will use it in all their projects because that framework is already known by them. For example for all projects that needs to persist data they will go for NHibernate even if Entity Framework could be also a good solution – or a NoSQL solution like MongoDB. Another good example is related to SPA frameworks. If they started to use a specific one, than they will stick on it without looking around.

What can happen in this cases?
Well first of all, if you don’t investigate what frameworks/solution could be used to resolve for a given problem you can end using the wrong solution. For example you can end up with an ORM framework that don’t have support for lazy loading, even if this is an important feature for you. You’ll start to do different hacks to support that features.
The interesting thing is that you will reuses that hacks for other projects also. You end up in a vicious circle that will hide the real problem that you have.
In this moment new frameworks and solution appears like mushrooms. Every year new stacks are available on the marker. When you stop looking around and stick on only one solution you are in a train with only one direction – to disaster. In a few years you will provide deprecated solution, on frameworks that are not supported anymore my community or producer.

What you can do to avoid this problem?
The simplest solution is to look around and know what is happening around you. Even if the new solutions are not the best, they may be interesting from different perspective and in time that solution could be better than the one that you already use.
Every time when you start a new project, don’t use the default setup template that you have in mind. For example .Net 4.5, EF, ASP.NET MVC, WCF, Angular.JS. Other solutions could be better that the default setup. Try to investigate what solutions are on the marker and what is the best for your project.
Don’t be afraid of learning curve. This is something normal and you can only benefit from it. Better solution, thinking outside the box, team with more skills, take our of the conform zone the team.

Conclusion
Never stick on a solution/stack because this is what you already know. This will limit you as a person, team from the skills perspective, company from the quality and innovation perspective and the solution that you provide that might not be the best one.

Comments

Post a Comment

Popular posts from this blog

How to audit an Azure Cosmos DB

By
In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...
Post a Comment
Read more

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills)

By
Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills) The idea that moving to the cloud reduces the costs is a common misconception. The cloud infrastructure provides flexibility, scalability, and better CAPEX, but it does not guarantee lower costs without proper optimisation and management of the cloud services and infrastructure. Idle and unused resources, overprovisioning, oversize databases, and unnecessary data transfer can increase running costs. The regional pricing mode, multi-cloud complexity, and cost variety add extra complexity to the cost function. Cloud adoption without a cost governance strategy can result in unexpected expenses. Improper usage, combined with a pay-as-you-go model, can result in a nightmare for business stakeholders who cannot track and manage the monthly costs. Cloud-native services such as AI services, managed databases, and analytics platforms are powerful, provide out-of-the-shelve capabilities, and increase business agility and innovation. H...
Post a Comment
Read more

Cloud Myths: Migrating to the cloud is quick and easy (Pill 2 of 5 / Cloud Pills)

By
The idea that migration to the cloud is simple, straightforward and rapid is a wrong assumption. It’s a common misconception of business stakeholders that generates delays, budget overruns and technical dept. A migration requires laborious planning, technical expertise and a rigorous process.  Migrations, especially cloud migrations, are not one-size-fits-all journeys. One of the most critical steps is under evaluation, under budget and under consideration. The evaluation phase, where existing infrastructure, applications, database, network and the end-to-end estate are evaluated and mapped to a cloud strategy, is crucial to ensure the success of cloud migration. Additional factors such as security, compliance, and system dependencies increase the complexity of cloud migration.  A misconception regarding lift-and-shits is that they are fast and cheap. Moving applications to the cloud without changes does not provide the capability to optimise costs and performance, leading to ...
Post a Comment
Read more