Archive for the ‘Dedicated Development Team’ Category
Introducing ASP.NET Core:
ASP.NET Core is a new open-source and cross-platform framework for building modern cloud based internet connected applications, such as web apps, IoT apps and mobile backends. ASP.NET Core apps can run on .NET Core or on the full .NET Framework. It was architected to provide an optimized development framework for apps that are deployed to the cloud or run on-premises. It consists of modular components with minimal overhead, so you retain flexibility while constructing your solutions. You can develop and run your ASP.NET Core apps cross-platform on Windows, Mac and Linux. ASP.NET Core is open source at GitHub.
The framework is a complete rewrite that unites the previously separate ASP.NET MVC and Web API into a single programming model.
Despite being a new framework, built on a new web stack, it does have a high degree of concept compatibility with ASP.NET MVC.
ASP.NET Platform exists for more than 15 years. In addition, at the time of System.Web creation it contained a large amount of code to support backward compatibility with classic ASP. During this time, the platform has accumulated a sufficient amount of code that is simply no longer needed and is deprecated. Microsoft faced a difficult choice: to abandon backward compatibility, or to announce a new platform. They chose the second option. At the same time, they would have to abandon the existing runtime. Microsoft has always been a company focused on creation and launch on Windows. ASP.NET was no exception. Now the situation has changed: Azure and Linux occupied an important place in the company’s strategy.
The ASP.NET Core is poised to replace ASP.NET in its current form. So should you switch to ASP.NET Core now?
ASP.NET Core is not just a new version. It is a completely new platform, the change of epochs. Switching to ASP.NET Core can bring many benefits: compact code, better performance and scalability. But what price will be paid in return, how much code will have to be rewritten?
.NET Core contains many components, which we are used to deal with. Forget System.Web, Web Forms, Transaction Scope, WPF, Win Forms. They no longer exist. For simple ASP.NET MVC-applications changes will be minor and the migration will be simple. For more complex applications, which use a great number of .NET Framework classes and ASP.NET pipeline situation is more complicated. Something may work and something may not. Some part of the code will have to be rewritten from scratch. Additional problems may be caused by WebApi, because ASP.NET MVC subsystems and WebAPI are now combined. Many libraries and nuget-packages are not ready yet. So, some applications simply will not have a chance to migrate until new versions of the libraries appear.
I think we are waiting for the situation similar to the transition from Web Forms to ASP.NET MVC. ASP.NET Framework will be supported for a long time. First, only a small amount of applications will be developed on ASP.NET Core. Their number will increase, but sooner or later everyone will want to move to ASP.NET Core. We still have many applications running on the Web Forms. However, no one comes to mind to develop a new application on the Web Forms now, everybody chooses MVC. Soon the same happens to ASP.NET Framework, and ASP.NET Core. ASP.NET Core offers more opportunities to meet modern design standards.
The following characteristics best define .NET Core:
- Flexible deployment: Can be included in your app or installed side-by-side user- or machine-wide.
- Cross-platform: Runs on Windows, macOS and Linux; can be ported to other OSes (Operating Systems). The supported OSes, CPUs and application scenarios will grow over time, provided by Microsoft, other companies, and individuals.Command-line tools: All product scenarios can be exercised at the command-line.
- Compatible: .NET Core is compatible with .NET Framework, Xamarin and Mono, via the .NET Standard Library.
- Open source: The .NET Core platform is open source, using MIT and Apache 2 licenses. Documentation is licensed under CC-BY. .NET Core is a .NET Foundation project.
- Supported by Microsoft: .NET Core is supported by Microsoft, per .NET Core Support.
- As for the “cons” one of the biggest issues are gaps in the documentation. Fortunately most of the things for creating and API are covered, but when you’re building an MVC app, you might have problems.
- Next problem – changes. Even if you find a solution to your problem, it could have been written for a previous version and might not work in the current one. Thanks to open source nature of it, there is also support available on github. But you get same problems there (apart from searching).
- Another thing is lack of support in the tooling. You can forget about NCrunch or R# Test Runner. Both companies say they will get to it when it gets more stable.
- ASP.NET Core is still too raw. Many basic things, such as the Data Access, is not designed for 100%. There is no guarantee that the code you are using now will work in the release version.
- It’s modular. You can add and remove features as you need them by managing NuGet packages.
- It’s also much easier and straightforward to set up.
- WebApi is now part of the MVC, so you can have class UserController, which will return a view, but also provide a JSON API.
- It’s cross-platform.
- It’s open-source.
ASP.NET Core is the work on the bugs of the classic ASP.NET MVC, the ability to start with a clean slate. In addition, Microsoft also aims to become as popular as Ruby and NodeJS among younger developers.
NodeJS and ASP.NET have always been rivals: both – a platform for backend. But in fact, between them, of course, there was no struggle. The new generation of developers, the so-called hipster developers, prefer Ruby and Node. The adult generation, people from the corporate environment, are on the side of .NET and Java. .NET Core is clearly trying to be more youthful, fashionable and popular. So, in future we can expect the .NET Core and NodeJS to be in opposition.
In its advertising campaign, Microsoft is betting on unusual positions for it: high performance, scalability, cross-platform. Do you think that ASP.NET “crawls” on the territory of NodeJS? Please feel free to share your thoughts with us.
Thank you in advance!
Business Development Manager | LI Profile
In IT world everybody knows what Dedicated Development Team approach implies. Right now take half a minute and try to describe your associations with DDT:
Hmmm…5 developers… more?.. big project…half a year or longer… long negotiations…administrative formalities…we will start in a month?…Hmmm…maybe we are too small for this… That’s what most probably has come to your mind first.
Indeed, not so long ago DDT model was considered a long-term, continuous, stiff cooperation approach. That’s how it classically looks like. Still now we are not longer in the era of big-big system projects prevalence and large companies domination. Large basic systems have already been developed, the majority of companies in the market are SMBs and start-ups. It’s evident that today’s reality dictates new standards for cooperation approaches. And outsourcing is adapting to newly arising demand specifics as well.
Since average project looks differently now, DDT model is undergoing changes too. Today the dialogue between customer and vendor runs like this, at least at Altabel:
– We’ll need 3 Java developers for the server part. There will also be iOS mobile client part, so 1 iOS developer? And Android client will follow…Also our target audience has demand for Windows Phone….Yeah…
– Ok, let’s agree on an approximate schedule for these assignments. We will pick candidates for you.
-Maybe testers for active testing before releases…
-From time to time? On a short notice, that’s Ok.
– What if we start with one developer only?
– No problem. Decide when.
– Have work in 1-2 weeks already…
– Review CVs please and we’ll arrange interviews. Simultaneously, let’s discuss contractual terms.
-Oops, we need to integrate with a highly specialized service. We need to add specific skills to already established core team. Great to have it all together…
– Which skills? Will try to find them too, in our or partner’s pool.
-Our product needs new technology. In-house team is taking on this strategic task, but they can’t keep up with supporting the current system… Still our users need decent level of support service!
-We may assist with maintaining your system working stably.
– Have a project vision, but details are still emerging. Looks like elaborating an accurate spec will take ages, but need to start soon since the market won’t wait…
-We may assign a dedicated specialist to elaborate all the details along with you and perhaps prototype for you. Then approach may be changed if you still wish so.
-But the developer’s engagement will be for this project timeframe only?
I guess flexibility becomes an inalienable characteristic of Dedicated Development Team approach. Now it’s just “folk” and is adaptable to a particular company, project or condition.
Let it be a womanly sounding comparison, still this is like with clothes: casual is popular nowadays🙂 so dress your company in a new comfortable “casual” DDT style!
Thanks for attention. Your comments are appreciated, as usually🙂
Helen Boyarchuk – Business Development Manager (LI page)
Helen.Boyarchuk@altabel.com | Skype ID: helen_boyarchuk
Altabel Group – Professional Software Development
Gartner’s outsourcing tip: “Don’t just seek the leaders blindly – determine which vendors are the right fit for your organization”
Posted July 7, 2011on:
The debate on the success of outsourcing as an industry seems to last endlessly. Over the years outsourcing contracts underwent a lot of changes – as the result we now see more multi-sourcing engagements and smaller focused contracts. In fact outsourcing contracts shrank in length or value per contract, but the relationship with the client has endured. Indeed, it’s relations, not size that matters. So, recently the issue of a choice of a right vendor for an outsourcing contract has become even sharper and vital for a larger number of companies in IT industry.
Many organizations that want to outsource IT services are intimidated by the task of determining which location in general and vendor in particular would best suit their requirements. Many researches in the field have been made. If in the early days of outsourcing price level was the weightiest criterion, now determination of an outsourcing partner and their geo-location is based on a whole system of criteria including not solely cost competitiveness based ones but key statistics on resources and skills level, country’s business and economic environment. Among them you may see English (French, German, etc) language skills, educational system quality, cultural compatibility, political and economic environment, global and legal maturity, and data and intellectual property security and privacy.
Historically such low-cost locations as India for instance were very popular offshore outsourcing destinations, still recently with the maturation of IT domain and with recent wage inflation and educational challenges these locations have receded their position as outsourcers now expect more “added value” to their projects and business. In this respect more attention is paid to Eastern European region, especially by Western and Northern European companies. Germany, Switzerland and Austria along with the Nordics in particular perceive Eastern Europe as a favored nearshore destination. Eastern Europe ranks high in terms of efficiency of technical education, work ethics and cultural sensitivity adding to the region’s geo-attractiveness as a base for outsourced activity.
Many respectable researchers think in the next ten years it is likely that Eastern Europe will move out from being an ‘emerging destination’ to a ‘key destination’ for outsourced activity: even though facing continued cost pressure from Indian market and despite being largely ‘overlooked’ by US based outsourcing providers, it is expected to proceed receiving its share of traditional high end software engineering and other IT services, from Western and Northern Europe. Many who experienced outsourcing there are characterizing Eastern Europe (Lithuania, Russia, Belarus, Ukraine, etc) as [a good place to find low cost, technically superb coders,.. generally hard workers, honest in answers to any your questions and strategically thinking].
Anyway, all these ratings of outsourcing locations are just generalization – anywhere you may find good and worse executors. As Gartner tips: “Don’t just seek the leaders – determine which vendors are the right fit for your organization”.
Well, perhaps very generally it would be a bad idea to hire designers from South East Asia if you expect a Western looking result🙂, still efficiency of an IT service provider should be checked in each particular case. There are a couple of advises helping to choose a good provider:
– Choose companies who have good feedback, ratings and recommendations. If a company follows market trends, makes marketing and technical researches, has good recommendations, especially from the companies from your geo-region, these all mark quite a solid level of credibility.
– Be careful about generic responses. This mostly concerns a stage when particular project details/requirements are already discussed. The tip considers both parties actually🙂
– Start cooperation with a relatively small test/pilot project to evaluate provider’s competences. Altabel Group’s experience shows it’s natural for our clients to develop a pilot project with us to confirm our competences and then organically move on to Dedicated Development Team model for further cooperation.
– Try to meet your partners personally at initial stages of cooperation. Arrange short trips to visit a provider and especially meet your team members face to face.
– Think “potentially”. Keep contact information of those companies whose responses you liked for future references even if they do not fit your current project requirements.
And what are tips from personal experience? When does outsourcing have the best chances to succeed or fail? Do you have any preference in terms of a region to outsource from?
You are welcome to share your opinions here.
Helen Boyarchuk – Business Development Manager (LI page)
Helen.Boyarchuk@altabel.com | Skype ID: helen_boyarchuk
Altabel Group – Professional Software Development
Over the past several years, offshore outsourcing has really seen an upsurge. Leading companies have felt that appointing an offshore service provider who has an experienced team of developers, was an excellent way to get their projects completed without commitment to the salary, benefits, and obligations that go along with hiring an in-house employee.
Altabel Group is an EU software development and consulting company specializing in creating dedicated teams for customers. For a few years already our company has been practicing this model by creating core teams with customer requirements and project specifics in mind and ensuring that each team becomes a virtual extension of a customer in-house software team. As we see this model seems to be working nicely both for large businesses and start-up companies.
The Altabel Group model is offering the following opportunities:
- Increase of the company by virtually extending it but with almost zero hiring effort without incurring the costs of a full-time employee;
- Meeting the budget constrains by providing lower prices for development;
- Fexibility to obtain full or part-time resource solutions on demand and to have access to highly specific software technologies expertise on demand.
Currently this is one of our most heavily requested services to provide a full team to cover ongoing development, bug fixing and support. This service gives maximum flexibility to our clients and allows them to optimize the teams’ activities to suit their current business requirements. By being free to expand or reduce the team by necessity a client defines the project workload and thus pays for effective hours only and avoids idle hours. The customer defines the team composition, its structure and technical experience needed specifically for a concrete project. It should be mentioned that the team could start from 1-2 developers and try a pilot project first so that a customer could make sure of our services quality and developers performance and experience.
At the moment our company is offering its services at discounted rates, therefore it could be just the right time for considering our proposal and starting with a test project to evaluate quality we provide.
Hope the above makes sense to you. If our company approach and software development services seem interesting to you, you are free to contact us or leave your comments here.