<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by FlexBase on Medium]]></title>
        <description><![CDATA[Stories by FlexBase on Medium]]></description>
        <link>https://medium.com/@flexbasenet?source=rss-1a5eb25a7718------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*a6T_kIjfnAVRoV2davsfyw.png</url>
            <title>Stories by FlexBase on Medium</title>
            <link>https://medium.com/@flexbasenet?source=rss-1a5eb25a7718------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 21:24:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@flexbasenet/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[5 essentials for CEOs of software services companies working on digital transformation projects]]></title>
            <link>https://medium.com/@flexbasenet/5-things-you-should-know-as-ceo-of-an-software-outsourcing-company-if-your-teams-are-working-on-1f1e4d975aa1?source=rss-1a5eb25a7718------2</link>
            <guid isPermaLink="false">https://medium.com/p/1f1e4d975aa1</guid>
            <category><![CDATA[ceo]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[outsourcing]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[dotnet]]></category>
            <dc:creator><![CDATA[FlexBase]]></dc:creator>
            <pubDate>Mon, 30 Sep 2019 05:29:37 GMT</pubDate>
            <atom:updated>2019-10-01T09:58:08.817Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3TANcFDn4U7bqvA1hpq75A.jpeg" /></figure><p>1<strong>.</strong> <strong>Make sure your client’s top management is deeply invested in the digital transformation project:</strong></p><p>If your client’s top management is not deeply invested in the digital transformation project like it’s an important new business, 99% chances that the project will run into trouble very soon.</p><p>Digital transformation project is bound to hit an obstacle. And when that happens, because the top management is not invested fully, the project will be called off or trimmed down. And as an outsourced software team, you will be the first victim to be shown the way out of the door.</p><p>Digital transformation is not same as digital automation. Digital automation has a definite goal. And most of the time you have clear (or vague) idea about the development &amp; support timelines. But not in case of a digital business. A digital business will have shifting goals with continuous development as norm. This means it is a long-term hustle.</p><p>Therefore, the client’s business team should be investing in it like a new business.</p><p>If they treat it as an IT or software project which will somehow start making them money once the software is up in production server, you are headed for a crash. Educate the client team early on. Make sure you are embarking on a journey with a business team that is not afraid of the long term hustle.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7tMThIqq1kb4Wj0VH48_uw.jpeg" /></figure><p>2. <strong>Assure your clients that you are invested there for long term:</strong> If you are there for quick money — build software, do a cloud migration or install a product — it’s OK. You may do that.</p><p>But assuming you want a bigger play, you need to assure your clients that you offer long term benefits.</p><p>How to do that?</p><p>You need to show this in your pricing, project methodologies, in house-talent, engagement model and tools &amp; frameworks that you use.</p><p>If you are presenting the usual software development pricing &amp; engagement, the signal is clear you are have not understood the digital transformation life cycle.</p><p>Two drawbacks of this approach. You will have to compete with other low-priced vendors. And when change strikes, you will be the first one shown the way out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VZxPJhSo2GzdJLIfkpp50w.jpeg" /></figure><p>3. <strong>Think like an investor:</strong> You need to treat digital transformation projects like how an investor would treat start-up portfolios. First, you need to plan for a long-term hustle. Your pricing and engagement terms need to reflect that understanding. Second, you need to invest in many digital transformation projects. Not one.</p><p>Maybe not all your digital transformation projects will get resounding 100X success. But the ones that do, will more than compensate for your profits. This is investing in 100-X model.</p><p>The more digital transformation savvy you are, more are the chances that your customers will succeed.</p><p>Here’s the thing… Unlike an investor, you are not helpless in this whole scenario. A big onus of success is on you. You can drive the success by delivering value.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YQ-6TPowWRWgSnNg4-cilw.jpeg" /></figure><p>4<strong>.</strong> <strong>You need to lead the change</strong></p><p>Digital business is all about changing targets. It demands change as a norm. Are you skilled to meet this demand?</p><p>On ground it means, you cannot succeed relying on a traditional software engagement model.</p><p>This means you need to set your operations so that your delivery is innovation and change oriented.</p><p>How do you do that?</p><p>It comes down to leverages you can pull. You should provide tools, frameworks &amp; templates to your teams such that they can get the usual 80% software development stuff done without much effort.</p><p>This leaves you with the remaining ever growing 120% (no error here) that needs your 80% effort.</p><p>This way you will have time, money and resources to focus on innovation.</p><p>Also, you cannot think through everything in the beginning. You need to give enough room for juggling with resources and technology.</p><p>Can you provide leadership for this kind of environment?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CdqWuYdjDhLtra7lAj_KJw.jpeg" /></figure><p>5. <strong>Amass business, domain &amp; integration knowledge — have cross function teams</strong></p><p>You need to have domain experts in-house. If you don’t have them already, get your tech team to start building domain related knowledge documents based on their experience in projects. You can create a techno functional expert career path for techies.</p><p>Find ways to retain and share this knowledge within the company. Build processes around it.</p><p>Cross functional teams on the ground, is the way of digital leaders who can innovate and deliver value-adds to their clients.</p><p>_________________________________________________________________</p><p>Your involvement and investment as CEO in a digital transformation project is critical. You need to provide right leadership. If you are not invested, you will not gain from it.</p><p>Unlike a typical software project or automation project where you have a linear trajectory of building software in silos, in digital business you have to be always up for change in the plan.</p><p>Are you a CEO of a software outsourcing company? What are the challenges you face in digital transformation projects?</p><p>Have you provided the on-going continuous software development model to any client? How have you fared? What improvements in your model can you do?</p><p>Do let us know your views.</p><p>We are Flexdex, the communication and marketing arm of Flexbase.</p><p>Flexbase is a modern software architecture framework on top of .NET for building backend applications that have clean architecture out-of-the-box. Using Flexbase, you can complete 80% of your development requirements very fast. You can add and iterate new features easily. You can extend applications without regression issues. The tech teams can easily collaborate with business teams using the tools provided by Flexbase.</p><p>Would you like to know more about Flexbase for powering your digital transformation projects? Write to us a flexbasedigital@sumerusolutions.com</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f1e4d975aa1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[As businesses transform to digital businesses, what does it mean for the software solution…]]></title>
            <link>https://medium.com/@flexbasenet/as-businesses-transform-to-digital-businesses-what-does-it-mean-for-the-software-solution-d610e803a223?source=rss-1a5eb25a7718------2</link>
            <guid isPermaLink="false">https://medium.com/p/d610e803a223</guid>
            <category><![CDATA[outsourcing]]></category>
            <category><![CDATA[dotnet]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[ceo]]></category>
            <dc:creator><![CDATA[FlexBase]]></dc:creator>
            <pubDate>Mon, 16 Sep 2019 11:31:16 GMT</pubDate>
            <atom:updated>2019-09-18T09:56:14.136Z</atom:updated>
            <content:encoded><![CDATA[<h3>As businesses transform to digital businesses, what does it mean for the software solution providers</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mJSsIijOb9m66g98m7so-A.jpeg" /></figure><p>Jeff Gothelf &amp; Joshua Seiden, authors of <a href="https://amzn.to/2LlX3ZG">Sense &amp; Respond</a> (<a href="https://amzn.to/2LlX3ZG">amazon.in</a>), give example of a Bull semen provider company that has digitized its business successfully.</p><p>The company targets its audience, the digital-age Google savvy farmers, by informing them how to breed calves selectively using insemination techniques. When farmers visit the company website, they get a tool that helps them search, select &amp; buy a suitable bull semen by selecting desired progeny traits.</p><p>But this is not where it ends.</p><p>The company has a warehouse where the bull semen is stored in straws. The workers in the warehouse get the order from the website directly on their mobile apps for fulfillment &amp; shipping. Using the app, the workers appropriately package and ship the semen to the farmers.</p><p><strong>Digital Business is not Automation</strong></p><p>This was an example of how more and more businesses are transforming into software businesses. Or, digital businesses to be precise.</p><p>Digital businesses have learnt what it takes to succeed in the age of digital disruption. It is no more about running a software department in silo….</p><p>They know that a digital business requires them to tightly integrate digital tech into their business strategy.</p><p>In the Bull semen provider example, the company found new better ways of reaching out to their audience. When farmers landed on their website, they offered them a unique service. This service was built around the company’s unique knowledge of the product.</p><p>Digital businesses are meaningfully integrating digital technology with their products. It is not just a warehouse automation or an office automation. It is much more than that. They create differentiated services by combining their unique knowledge with digital tech.</p><p>Takeaway — there is big difference in just automating business processes vs creating &amp; running a digital business.</p><p><strong>Digital businesses are driven by change. &amp; They don’t exist in silo…</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/730/1*n25MlPlYWDUeB-nslqX6UQ.gif" /></figure><p>The software service providers need to understand that underlying driver in digital transformation is continuous change &amp; improvement of software.</p><p>Businesses who are adopting digital transformation want software to be responsive to the market needs. And in digital world, market needs could be influenced by what’s happening there in other markets.</p><p>For example, consider the user behavior in using digital products. Interaction preferences and habits of users are determined by what they are learning when interacting with B2C apps.</p><p>Jeff and Josh give an example of gas pipeline layout app that was built by a company for internal use by their employees. The app failed because it did not provide an interface like Google Maps.</p><p>The employees were expecting the gas pipeline map to have pinch and spread feature like Google maps.</p><p>This means besides building new features, improving &amp; changing the behavior of existing features becomes an important aspect for a digital business.</p><p>This is one of the main reasons of success of digital giants like Amazon, Uber and Facebook.</p><p><strong>New software development paradigm — continuous development</strong></p><p>Most of the software service providers see software development as one-time activity of building a large volume of features that must be ready by a launch date. And anything done after that falls in maintenance.</p><p>If there are feature changes or new feature demands after the launch date, those go in the change request (CR) or extension buckets. If it is T&amp;M arrangement, change request (CR) is money for the provider and expense for the customer. And soon CR becomes the most dreaded word…</p><p>But in digital business world, the rules are very different…</p><p>The rules of change requests are no more applicable. Rather you can think of digital business as change requests gone mainstream.</p><p>In digital business, there is continuous response available from the market. This means business can be improved by making changes in the software.</p><p>Is a change request model viable option in this environment? We don’t think so.</p><p>The paradigm of software development has changed.</p><p><strong>The real value is in continuity</strong></p><p>Ok. Let’s take a step back…</p><p>We are not suggesting that in future the usual way of software development will cease to exist. There is a need to build and release the software in traditional way. Like launching a software in cloud for the first time.</p><p>But the question that software service companies need to ask is — is that all they want to do? Where is the real value in a digital business or a digital transformation project?</p><p>Building and maintaining software is just the 10% of the digital business. It is just the start.</p><p>The real 90% value is in the changes that happen afterwards that make the business tick.</p><p>This means, what is going to differentiate software service providers who make it big in a digital transformation paradigm vs those who will very fast get marginalized, is their responsiveness to this changing nature of digital businesses. Can you create a service which is win-win: for you and for your customers in the long run?</p><p>For example, consider an e-commerce shop. As a software vendor, suppose you helped them build a site on cloud using a .NET Core 3 based monolithic software architecture. Of course, the work was quick and e-commerce site soon became popular.</p><p>Within a couple of years, the e-commerce site sees a huge surge of traffic on the site. Soon you realize, that the site needs to be moved to a micro-services architecture, if it must meet the rising traffic and feature upgrade demands.</p><p>Is this a change request?</p><p>For a traditional software business, it is.</p><p>But for a new digital age software services provider it is a natural progression which it has accounted for. By taking an evolutionary architecture approach, the software provider not only responds to the digital business’s need on a timely basis, it also saves enormous cost.</p><p>Here, do you see an opportunity or challenge?</p><p><strong>Opportunities and Challenges …</strong></p><p>Given this new nature of digital business, what are the opportunities and challenges for the software service providers,</p><p>Let’s look at opportunities first:</p><p>1. As more companies opt for digital transformation, there will be greater demand for outsourced partners to create custom software. This means more projects for software service providers.</p><p>2. <strong>There is a chance to differentiate by providing better and flexible services</strong>. The digital age businesses are not looking for conventional software partners, but partners that can contribute to their business on a continuous basis. They want partners who are invested in the business growth, i.e., software companies who can think through new features, future software needs, keep up with trends, suggest new improvements and be strategic partners in growth of the business.</p><p>3. <strong>Bring in new tools and innovation into play</strong>. Software companies have years of experience in building software. They can apply this knowledge in creating new tools and features as value adds for their customers.</p><p>4. <strong>Create products</strong>. Software services providers can look at trends and come up with innovative products that provide services to their group of customers.</p><p>But there are a few challenges,</p><p>1. <strong>Talent hunt becomes fierce</strong>. As more and more conventional businesses go digital, they would like to hire the best talent. This can lead to attrition and lack of good talent in the market for conventional software companies.</p><p>2. <strong>Turning in-house for best work</strong>. Some companies might choose to do big chunk of important work in-house rather than outsourcing to companies that do not provide strategic advantage. If as a software provider you fail to own the business growth KPIs, then aren’t digital businesses better-off owning the software development work in-house?</p><p>3. <strong>Consumed by digital businesses.</strong> The companies that are not ready to partner with clients on business results might find it difficult to survive or will get consumed by digital businesses.</p><p>4. <strong>Cannot bill conventionally</strong>. Software businesses need to change their pricing and billing strategies. They need to provide an innovative pay-as-you-go pricing model or a fixed pricing model for a larger set of features. This change might not come naturally to many software companies.</p><p>5. You can no more off-load bench time on to different clients.</p><p><strong>To win, change the way you build software</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LYlLIl5Esq-NPbzeCtkHxQ.jpeg" /></figure><p>How do software services providers make use of opportunities and turn around the challenges?</p><p>You need to change how you build software. Here are some tech, operational and business options we have put together for you to consider. Some are obvious. Some need serious rethinking,</p><p>1. <strong>Focus on architecture</strong> — in recent times clean architecture has gained a lot of traction. Digital success depends and low technical debt and ease of extensibility. One of the best ways to achieve low cost of extensibility is by designing clean evolving architecture.</p><p>2. <strong>Focus on NFRs early on</strong> — If you do not focus on NFRs early on, you will not be the preferred choice of your clients for long. High performance, scalability, maintainability and extensibility are bare minimum requirements of digital businesses.</p><p>3. <strong>Master CI/CD</strong> — Key component of continuous software development is continuous integration and continuous delivery. There are no second thoughts on this one.</p><p>4. <strong>Focus on innovation &amp; value adds to business</strong> — Software providers need to spend more time on improving existing features, creating high value features and innovating on behalf of the customers. This is where the digital businesses will put most of their money. Regular features should be fast and easy to come by. While money should be made in improvements, new features and innovations.</p><p>5. <strong>Think like an investor</strong> — Build a portfolio of digital transformation projects. And be invested in the success of these projects.</p><p>6. <strong>Adopt cloud</strong> — Cloud has many advantages. The biggest being low running cost. And others being — ease of scaling and ease of integration. When you pass on these benefits to your end customers, it works out better for you.</p><p>7. <strong>Focus on skill upgrade</strong> — You must focus on upgrading skills of your teams continuously. A team with latest skills in frameworks, tools and technologies is more likely to succeed in digital transformation projects.</p><p>8. <strong>Amass domain &amp; business knowledge</strong> — This is the only way you can design innovative solutions for your customers. You can pass the advantage of domain know-how to your customers in form of innovative features.</p><p>9. <strong>Innovative billing options</strong> — Most of the customers now want to go for fixed price for a given scope of work. Yet they want more features to be delivered with better quality. You need to offer better billing options.</p><p><strong>Summary — Innovators will win</strong></p><p>In short, while the volume of software development work is on rise, only those software services companies that can link their success to digital business success are likely to succeed in future.</p><p>Digital businesses are very different from businesses that use software for automating a process. Digital businesses evolve their software features with changes in the market. That’s where value is generated. Can you assure your clients that you will be there with them throughout this journey?</p><p>Those software service providers who change their focus from one-time delivery of software to delivering continued value to digital businesses, will have a bigger play.</p><p>Others will continue to struggle in L1 bids.</p><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><p><strong>Your views:</strong></p><p>Did you like this article? If you are a freelancer or work with a software services provider, where do you think your services can improve to take advantage of the new digital business paradigm? What will differentiate you? What services will you provide to digital business clients? Which tools and frameworks can help you in achieving continuous software development and innovation?</p><p><em>This article is published by Flexdex, the communications and marketing desk of Flexbase.</em></p><p><em>Flexbase is a modern age enterprise application framework that makes it very easy to build digital application using .NET. It helps software architects and developers focus on creating features and innovations rather than getting caught up in plumbing work. With a clean architecture at its core, Flexbase is ideal for building complex back-ends for modern digital applications.</em></p><p><em>If you are interested in knowing more about Flexbase, write to us at — flexbase@sumerusolutions.com</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d610e803a223" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Top 5 trends of .NET in 2019 that every Developer should know]]></title>
            <link>https://medium.com/@flexbasenet/top-5-trends-of-net-in-2019-that-every-developer-should-know-c97544b3754d?source=rss-1a5eb25a7718------2</link>
            <guid isPermaLink="false">https://medium.com/p/c97544b3754d</guid>
            <category><![CDATA[dotnet]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[microsoft]]></category>
            <category><![CDATA[developer]]></category>
            <dc:creator><![CDATA[FlexBase]]></dc:creator>
            <pubDate>Tue, 03 Sep 2019 09:41:08 GMT</pubDate>
            <atom:updated>2019-09-03T09:41:08.932Z</atom:updated>
            <content:encoded><![CDATA[<h3>Top 5 trends of .NET in 2019 that every Developer should know</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GPogIQvhNHw3XLxh44rd1g.jpeg" /></figure><p>It is an exciting time to be a .NET developer as the future of .NET is set to change. Even if you are not a .NET developer, it is hard to miss Microsoft’s announcement of the all-new .NET 5.</p><p>Pegged to be the future of .NET, the new framework is set to provide a unified platform for creating applications that are capable of running on platforms such as Linux and Windows, along with devices such as IoT and mobile. Updates such as these are set to affect your present enterprise application.</p><p>Let us look at the top four future trends in .NET that every developer should know.</p><h3>Trend 1: The Rising Popularity of .NET Core</h3><p>The recent updates by Microsoft have made .NET Core one of the hottest frameworks in the market. The .NET Core framework includes AOT, GC, Runtime, JIT, Base Class Library, ASP.NET, C#, ML.NET, VB.NET, F#, Entity Framework, WinForms, WPF, and Xamarin.</p><p>The upcoming .NET Core 3.0, which is set to release on September 2019 will include WinForms, WPF, and Entity Framework 6.</p><p>This will make it easier for developers to port desktop applications to .NET Core. .NET Core 3.0 will, however, not port further features from the .NET Framework.</p><h3>Trend 2 — The Famous Five — .NET 5</h3><p>All eyes are set on .NET 5 — the future of .NET. Microsoft is sunsetting ASP.NET web forms in .NET 5 and is currently recommending developers to migrate to Blazor or other alternatives such as Angular, React, and Vue SPA frameworks.</p><p>Windows Communication Foundation also didn’t make the cut, with the Redmond-based software provider suggesting developers use the gRPC framework.</p><p>Other technology stacks that have hopped on the .NET 5 bandwagon include Winforms, WPF, and UWP. All these technologies are being introduced to support desktop applications that work only on Windows.</p><p>A snapshot of what is new in .NET 5</p><p>● EF Core — EF 6 will be replaced by Entity Framework Core.</p><p>● ASP.NET Core — ASP.NET is replaced by ASP.NET Core.</p><p>● ASP.NET Core MVC — ASP.NET Core MVC unified ASP.NET MVC and Web API.</p><p>● MSIX — MSI package installer is being replaced by the new packaging tool for a desktop application.</p><p>● JsonDocument — json.net is being replaced by Json Document library from the System.Text.Json.JsonDocument.</p><h3>Trend 3 — Azure Application Development with .NET</h3><p>One of the major functionalities of .NET5 will be the development of Azure applications. More and more developers will continue to create software targeting Azure as they realize the amazing services provided by Microsoft Azure cloud development.</p><p>Azure comprises a blend of tools and frameworks such as docker containers, ASP.NET, serverless computing, microservices, data models and Azure databases, DevOps, Web API, and more.</p><h3>Trend 4 — Blazor</h3><p>Blazor, which began as an experimental project, is one of the hottest projects in the .NET community and has officially been launched by Microsoft.</p><p>It provides developers with a JavaScript alternative for web projects. A feature of ASP.NET, Blazor allows developers to create interactive Web UIs with C# instead of JavaScript. Since C# is used to write client and server code, it makes it easier for developers to share libraries and codes.</p><p>Blazor leverages WebAssembly to run client-side C# code directly in the browser or run it server-side. Exciting times on the open web lie ahead for developers as great work is happening in this area. It will be interesting to see how frameworks such as Razor Components/Blazor will or will not change the way developers write for the web.</p><h3>Trend 5 — ML.NET 1.2</h3><p>Just months after launching V1.0 of ML.NET, Microsoft has yet again updated its framework to add new features and functionality for developers.</p><p>The enhancements will help users to infuse machine learning functionalities into their applications with ease with the ML.NET 1.2. The upgrade now provides developers the ML.</p><p>Timeseries package for accurate forecasting and detecting an anomaly. It will also allow its users to use TensorFlow and ONNX models for deeper learning scenarios such as image classification, object detection, etc.</p><p>Among other major upgrade is the update of ML.NET CLI to 0.14 (preview) and availability of Microsoft.Extensions.ML integration package (preview) that allows easy integration with ML.NET models in web or serverless apps!</p><h3>What the Future Holds</h3><p>The future of .NET appears to be promising and exciting at the same time. The new .NET framework comprises all the necessary libraries, tools, and frameworks that are expected to ease the lives of developers.</p><p>For instance, learning JavaScript for SPA frameworks won’t be required since Blazor will be there to handle it. Similarly, developers won’t have to learn Python for machine learning because of the new ML.NET, Android or Swift because Xamarin is there to support it.</p><p>All you need to know is C# because it can be used to create applications that can run anywhere from IoT to Cloud. However, as .NET 5 comes into the picture, a lot of enterprise customers will be impacted if they have the product/framework based on WCF and WebForms.</p><p>So, if you are one of them, it is time to consider migrating to .NET Core because that is where the immediate future lies!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c97544b3754d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why .NET Can Be More Relevant to Start-Ups In 2019]]></title>
            <link>https://medium.com/@flexbasenet/why-net-can-be-more-relevant-to-start-ups-in-2019-e279f2479153?source=rss-1a5eb25a7718------2</link>
            <guid isPermaLink="false">https://medium.com/p/e279f2479153</guid>
            <category><![CDATA[microsoft]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[dotnet]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[developer]]></category>
            <dc:creator><![CDATA[FlexBase]]></dc:creator>
            <pubDate>Tue, 27 Aug 2019 07:26:31 GMT</pubDate>
            <atom:updated>2019-08-27T08:40:42.534Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why .NET Can Be More Relevant to Start-Ups In 2019</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nSr4xMHUAJ8BRGXMFr6WkQ.jpeg" /></figure><p>A lot has changed since .NET was introduced by Microsoft in the late 1990s. Since then, the tech giant has upped the ante on the framework and transformed it from being a locked-down framework into something freely available to developers. What changed the game for the Redmond-based company was the introduction of .NET Core, ASP.NET Core, and newer versions of C#, helping increase its stack adoption by a huge margin. Today, the .NET Core framework is cross-platform, performant, lean, and open-source. And this is one of the many reasons why startups have started embracing .NET to maximize their benefits in 2019.</p><h3>Why .NET?</h3><p>According to<a href="https://www.similartech.com/technologies/asp-net"> SimilarTech</a>, a total of 2.3 million websites and 1.7 million unique domains are being built on ASP.NET. Although this is a legacy figure, it demonstrates the user base that .NET and ASP.NET enjoy even today.</p><p>What is striking now is that t .NET / C # is picking up steam with the Redmond giant announcing the initiative, Bizspark/”Microsoft for Startups” to help startups benefit from developing and marketing business software products. This initiative encourages startups to reap the benefits of creating, developing, and marketing enterprise-level software. Microsoft will provide unlimited 3-year licenses to all their products and a free MSDN gold subscription.</p><p>Microsoft has also gone full throttle to make .NET and Xamarin open source projects, allowing developers to run .NET Core even on Linux. That’s not all; the company also bought the world’s biggest open-source community — GitHub. Gone are the days of tireless code developing on .NET framework. Today, the programming language has a code library that can be used to ensure a quicker and more efficient way of processing development. All these programs greatly reflect the company’s commitment to ease the pain of startups and become the preferred open-source among developers. Other reasons why .NET is here to stay are:</p><h3>Diversity and Versatility</h3><p>The two most enduring aspects of this high-performing program are diversity and versatility, making it a favorite of businesses across industries. The .NET ecosystem allows you to build pretty much everything with a single stack. You can now create desktop applications with UWP, cross-platform mobile apps with Xamarin, real-time applications with SingalR, web applications with ASP.NET Core, and the list goes on! All this gives you access to a coherent programming framework that is on par with today’s rapidly changing technological advances!</p><h3>Safety and Scalability</h3><p>.NET continues to be one of the most preferred frameworks among developers as businesses express growing concerns over data security and cyberattacks. ASP.NET is a comforting platform for most users because of its high-end security features.</p><p>The enhancements made to .NET Core have made it a highly scalable framework with a speedy development environment.</p><p><strong>World’s Most Popular IDE</strong></p><p>Add to it, the IDEs — Visual Studio and Visual Studio Code — that allow developers to build almost any app for any device. Visual Studio and Visual Studio Code offer world-class features to write and debug code and collaborate seamlessly easily. Bonus: Visual Studio Code comes with several Git commands and extensions for customization along with IntelliSense that allows smart completion of tasks based on function definitions, imported modules, and variable types.</p><p><strong>Interoperability</strong></p><p>.NET interoperability is unmatched since the framework is language-neutral and can work with any hardware or software, even the ones that have not been invented yet! Interoperability, which was once seen as a nice-to-have component, is now an essential feature for small and big businesses alike. With smart devices and the Internet of Things penetrating our daily lives, Microsoft realized the importance to empower developers to build their app/website that can be accessed across several competing platforms. By releasing the .NET framework as an open-source, the tech giant has paved the way by creating a language that is available on any machine and can handle any app development in almost all languages.</p><h3>Huge Developer Community</h3><p>Another major advantage of using .NET is a huge developer community available on<a href="https://stackoverflow.com/questions/tagged/.net?sort=frequent"> Stack Overflow</a>,<a href="https://github.com/dotnet"> GitHub</a>,<a href="https://aka.ms/csharp-discord"> C# on Discord</a>,<a href="https://gitter.im/dotnet/community"> Gitter</a>,<a href="https://www.dotnetfoundation.org/"> .NET Foundation</a>, etc. Whether you want collaboration solution for GitHub projects, ask general programming questions, or simply get inspired, the .NET developer community increases collaboration and connects like-minded developers around the world.</p><p>The community is continuously growing and in the past few years have created many open-source and paid developers tools and frameworks on top of .NET Core, that is helping developers and architects create better and better software products and solutions.</p><h3>“The Times, They Are a-Changin’”</h3><p>All the benefits mentioned above conclusively show why startups have started using the .NET Core in 2019. According to<a href="https://trends.builtwith.com/framework/ASP.NET"> BuiltWith</a>, a total of 29,331,196 live sites are using the .NET framework to operate businesses. It is without a doubt, one of the best in the market, especially if they want to remain competitive and relevant. As companies make innovative solutions and strategies, .NET will not only help them get recognized but also cut back on their operational costs and efforts. With .NET firmly in the realm of the open-source community and portable devices, there is virtually no end to possibilities for startups and developers alike. We are excited to see how Microsoft goes all guns blazing to ramp up .NET’s adoption further, are you?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e279f2479153" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What CEOs, CIOs should know about the power of APIs.]]></title>
            <link>https://medium.com/@flexbasenet/what-ceos-cios-should-know-about-the-power-of-apis-516624ed32e7?source=rss-1a5eb25a7718------2</link>
            <guid isPermaLink="false">https://medium.com/p/516624ed32e7</guid>
            <category><![CDATA[ceo]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[api-management]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <dc:creator><![CDATA[FlexBase]]></dc:creator>
            <pubDate>Mon, 15 Jul 2019 10:37:09 GMT</pubDate>
            <atom:updated>2019-07-15T10:41:03.947Z</atom:updated>
            <content:encoded><![CDATA[<h3>What CEOs, CIOs should know about the power of APIs. The opportunities, challenges, mechanics, and monetization.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mAK9wz78OxI7dT5lz_4MYA.jpeg" /></figure><h3>APIs Open Up Avenues for Revenue</h3><p>The power of APIs in keeping your IT systems relevant cannot be denied. Businesses are driven by how effectively they capitalize on their data, and APIs are a means of realizing and monetizing the potential of your data.</p><p>Companies like Uber and Ola make use of popular <a href="https://www.medianama.com/2016/03/223-google-maps-ola-integration/">map APIs</a> to power their navigation services, which enables the development team to work on other features.</p><p>Several more companies have adopted APIs as not just a part of their technical strategy, but their general strategy as well, as evidenced by the <a href="https://www.programmableweb.com/category/all/apis">21000+ APIs available on ProgrammableWeb</a>.</p><p>API-driven development has benefits like allowing your development and testing teams to work in parallel and speeding up the overall pace of development.</p><p>You will also be able to further bring down the Time-to-Market for new functionality added to a product by developing your product in increments powered by predefined APIs.</p><h3>The Power of APIs</h3><p>There are a plethora of benefits should you choose to design your IT systems using APIs. APIs are relatively easy to manage and scale, and they allow you to reuse services, reducing development efforts.</p><p>Using APIs also increases the ease of integrating modern-day innovations. For instance, integrating APIs into your IT systems should be the first step in your journey of moving your applications to cloud platforms, a move which would increase scalability and reduce the cost of operations.</p><p>APIs allow you to invite other vendors to innovate on top of your data should you have the prerequisite permissions from your customers.</p><p>In public systems which handle customer data, using APIs ensures that even though obtaining the appropriate desired data is easy, the data is retrieved securely and the access permissions are restricted.</p><p>So it comes as no surprise that in the European Union, as per <a href="https://www.evry.com/en/about-evry/media/news/2019/06/psd2-the-directive-that-will-change-banking-as-we-know-it/">PSD2</a> (the second Payment Services Directive), it is a mandate for banks to provide access to customer accounts via APIs.</p><p>Since APIs are being mandated in the banking sector in the EU, one can safely assume that they are going to revolutionize each sector in the market worldwide.</p><p>In a world where data is power, APIs are a means of harnessing the power of the data; no matter what the goal, APIs should be used to drive innovation.</p><h3>API Fundamentals: Must-Knows for all CXOs</h3><p>If you decide to take your company architecture’s down the microservices route, APIs will be the basic building blocks of your IT systems.</p><p>It is essential to familiarise yourself with common API architecture practices being followed in the industry as your API architecture will impact the stability of your services and the cost you incur.</p><p>Often, a microservice-based architecture in large organizations has three tiers, namely System Layer APIs (SAPIs), Process Layer APIs (PAPIs), and eXperience Layer APIs (XAPIs).</p><p>SAPIs retrieve data from the back-end system, PAPIs add business logic, and XAPIs is the layer that the front-end systems pull their data from.</p><p>Even though this has been proven to be the standard across the industry, this model can be adjusted to suit your company’s needs.</p><p>For instance, Netflix is a great example of a company that has a praiseworthy microservice-model.</p><p>Despite offering a complex service, their microservices are organized so as to reduce operational overheads while offering a seamless consumer experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZolgeDqO6hdL3Pj_nZUo8w.jpeg" /></figure><h3>The Make-or-Break API Challenges You Need to Know</h3><p>While the adoption of APIs sounds like the magical panacea for a company which has not yet implemented the latest technological innovations, if your company’s API adoption strategy falters at any step, the entire attempt could turn out to be an exercise in futility.</p><p>So, how could you overcome some of the most common challenges in an API-enablement journey?</p><ol><li><strong>Have a complete API-enablement journey charted out</strong></li></ol><p>It is essential to have a complete technology roadmap in mind and not just focus on a single aspect of transformation. You must involve stakeholders and architects while deciding the APIs to build to ensure that the right APIs are being prioritized.</p><p>By designing a proof of concept of an end-to-end API-enabled system, a lot of system-specific points to consider will come to light. This phase of deciding which APIs to design will be the most critical part of your company’s API-enablement journey.</p><p><strong>2. Make sure the team understands the goal of an API-enabled system and the rationale behind it</strong></p><p>The team must imbibe an API-first approach for future development. This will ensure the code that they write is extensible across multiple platforms and channels, making the systems future-proof and able to integrate all the latest innovations in technology.</p><p><strong>3. Build an appropriate API team</strong></p><p>It is critical to ensure that the APIs developed are not only generic enough to be usable across various functions but are also able to supply the exact requirements to each function.</p><p>This requires you to get an experienced architect to be on board, along with developers who have a thorough understanding of the back-end systems.</p><p><strong>4. Decide which APIs are being developed to deliver business value, and which for technical improvement</strong></p><p>This comes down to deciding who takes ownership of a particular API, the business team or the IT team.</p><p>APIs are going to be created for various reasons, but there should be a team that takes ownership of them.</p><p><strong>5. Make sure the APIs are discoverable, documented, and flexible</strong></p><p>The API documentation is just as critical as API development, as in order to adopt APIs, your developers must know how to use them.</p><p>The business team too can only drive the adoption of APIs if they can comprehend its functionality easily. The API documentation should also explain how APIs can be used across teams.</p><p><strong>6. Accept when it is time to discard a design/thought process and ask your developers to go back to the writing board</strong></p><p>It is inevitable that there will be multiple iterations of the API design journey, and this is something you must not shy away from. Initial revisions are better than regretting later.</p><p><strong>7. Understand the difference between API versioning and extending APIs</strong></p><p>A significant challenge your tech team will face is of creating new versions of APIs and managing these versions.</p><p>As your product grows, you might need to prioritize between providing uninterrupted services to your customers and providing new features and services. It is strongly recommended that you ensure the APIs are designed to be extensible from the beginning.</p><p>API development works best with an agile way of working; fail often, fail fast while developing incremental product updates to ensure the development is always aligned with the expected end-state.</p><h3>Are You up for It?</h3><p>APIs can be the drivers of business in the digital age. If you want to keep up with the fast pace of technology today and allow your services to scale, or if you want to build microservices and shift to cloud and open access to your data for innovation, building and managing APIs is going to be critical for your business.</p><p>Ignoring the significance of APIs would be a critical mistake, one that would cost more the later it was rectified. Ensure that you are ready to take on the challenge soon, and enjoy the all the benefits that APIs have to offer to your business.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=516624ed32e7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[10 Essential .NET Tools That Every Developer Should Have in Their Arsenal]]></title>
            <link>https://medium.com/@flexbasenet/10-essential-net-tools-that-every-developer-should-have-in-their-arsenal-6d12989a6130?source=rss-1a5eb25a7718------2</link>
            <guid isPermaLink="false">https://medium.com/p/6d12989a6130</guid>
            <category><![CDATA[dotnet]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[microsoft]]></category>
            <category><![CDATA[dot-net-tools]]></category>
            <category><![CDATA[aspdotnet]]></category>
            <dc:creator><![CDATA[FlexBase]]></dc:creator>
            <pubDate>Thu, 11 Jul 2019 10:29:38 GMT</pubDate>
            <atom:updated>2019-07-19T10:25:53.927Z</atom:updated>
            <content:encoded><![CDATA[<h3>10 Essential .NET Tools That Every Developer Should Have in Their Arsenal</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tNtI-fxgj2u2RGdUMjSbww.jpeg" /></figure><p>The popularity of the .NET framework has led to a sharp rise in the number of third-party tools. There is a treasure trove of free tools in the .NET world with most developers already using some well-known tools like Notepad++ editor and open source code sharing sites like <a href="http://sourceforge.net/">SourceForge.net</a>. These tools enable <strong>Dotnet developers</strong> to create intuitive applications and boost productivity. But selecting the right tool is easier said than done. More often than not, developers need to research a lot to find out what will work best for them, which is least to say, a very time consuming and tedious process.</p><p>To help save your time, we have compiled a list of our top 10 <strong>.NET development toolset</strong> that every developer should have in their arsenal. This blog will help the readers cut through the noise and choose tools that are widely favored by fellow developers around the world.</p><h3>1) Visual Studio</h3><p>Topping the charts of this list is the Microsoft Visual Studio, which is by far the most popular tool used by developers for designing different kinds of applications including mobile apps, as well as websites. <a href="https://www.infographicbee.com/net-development-trends-2018/">According to a recent study</a>, more than 41 million live websites have reportedly used .NET! Its visual studio extension strengthens the core VS functionality with features like task shortcuts and Intellisense for CSS/HTML/JavaScript, etc. A productivity booster, this extension edges out other <strong>Dotnet development toolset</strong> and is a must-have to write and debug code with ease.</p><h3>2) ReSharper</h3><p>This is a no-brainer. This tool not only helps developers perform on-the-go code analysis, but it also offers numerous quick-fixes and comes with automated code refactoring. Developed by JetBrains, ReSharper has more than 60 refactoring and 450+ context actions. It’s a handy tool for <strong>dot net developers</strong> who intend to quickly complete their projects and is also a hit amongst programmers who have only just discovered .NET.</p><h3>3) LINQPad</h3><p>LINQPad is a lightweight extension and is free to use. Any <strong>dot net developer</strong> can vouch for its efficiency. It is the number one platform to test LINQ queries or any C#/F#/Visual Basic program. LINQPad is popular due to its rich output formatting, optional auto-completion, and integrated debugging.</p><h3>4) NuGet</h3><p>A package manager for .NET, NuGet is a great addition to <strong>.NET development toolset.</strong> It allows developers to access third-party libraries and build or share their own tools. NuGet has more than 98,000 packages available, making it the largest database of third-party components for .NET. With this extension, developers can easily browse an unknown feed and create packages manually.</p><h3>5) ELMAH</h3><p>If you have a website in the works, then you need to have ELMAH to debug and log an error for ASP.NET. Provided by Google, this error logging module helps <strong>.NET developers </strong>identify gaps in their codes. The tool can be easily added to a running ASP.NET web app without the need for re-compilation or re-deployment.</p><h3>6) NDepend</h3><p>Another highly recommended tool for all <strong>dot net developers</strong> is NDepend. It helps programmers enhance the quality of their codes by using several metrics. This static analysis tool is a must-have for it also allows the visualization of the code’s design and helps estimate the technical depth of the IDE. NDepend offers a custom querying language that helps <strong>.NET developers </strong>to examine their application’s coupling and analyze how well they adhere to standards.</p><h3>7) .NET Reflector</h3><p>.NET Reflector is an absolute necessity for programmers who want a decompiler and static analyzer for its .NET framework. This <strong>essential tool for developers</strong> helps debug the .NET code, such as third-party components even if there are no documentation or comments. It also provides an insight into what the code does when decompiled and what an assembly contains.</p><h3>8) Fiddler</h3><p>When talking about dot net development tools, it is impossible to miss Fiddler. It allows developers to easily expose dynamic data grids and comes with customization features that can show data in a preferred view. Provided by Telerik, this invaluable .NET tool is used in between services and intercepts all communication.</p><h3>9) JSON Formatter</h3><p>Even though nearly all IDEs can format JSON files, the JSON formatter makes tasks a lot easier. JSON files can be difficult to read, and that is why the tool formats JavaScript Object Notation in a readable format, eventually making it easy to debug. This tool validates, formats, and gives an intelligible JSON output to the .NET programmers. The most popular free tool is the JSON Formatter &amp; Validator provided by Curious Concept.</p><h3>10) GitHub Desktop</h3><p>GitHub can be used with any Git repository, thereby providing a uniform cross-platform experience to its users. It makes us to our top 10 essential <strong>.NET development toolset</strong> for its visualization properties and the range of features it provides, including image diff support, strong community support, and extensive editor. And, the icing on the cake is that this extension doesn’t need any personal API tokens.</p><h3>Summing Up</h3><p>This was our list of 10 essential <strong>.NET development toolset</strong>. Ultimately, your choice will depend mostly on a specific project you are trying to complete. <a href="https://www.daxx.com/blog/development-trends/number-software-developers-world">More than seven million</a> <strong>dot net developers</strong> use these tools to automate several manual processes to save time and reduce human errors. The bottom line: no matter which are the tools that you choose, make sure that they allow you to complete a project without any errors and on time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d12989a6130" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Topic: 8 habits of successful architects who create easy to maintain software]]></title>
            <link>https://medium.com/@flexbasenet/topic-8-habits-of-successful-architects-who-create-easy-to-maintain-software-e9d56abcbe47?source=rss-1a5eb25a7718------2</link>
            <guid isPermaLink="false">https://medium.com/p/e9d56abcbe47</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[domain-driven-design]]></category>
            <category><![CDATA[clean-code]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[FlexBase]]></dc:creator>
            <pubDate>Tue, 23 Apr 2019 12:45:01 GMT</pubDate>
            <atom:updated>2019-04-23T12:45:01.012Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1003/1*k9kJB44tU4M3VI7Nxct9Xg.jpeg" /></figure><p>Maintainability as an attribute for quality software demands keen attention and planned actions from an early development stage. It is not really about the wise man’s advice of ‘a stitch in time saves nine’. It is rather about building a tapestry that can be stitched quickly, patched easily and doesn’t tear-off so often.</p><p><strong>THE SOFTWARE RENAISSANCE</strong></p><p>A smart software architect will always keep learning from other architects and developers.</p><p>It is like the work of the masons of the Renaissance era, who would amass precious knowledge while on the job, like how to carve different types of stones, how to use the tools optimally, how to create intricate shapes and designs and which tools need to be used when. And they would learn all of this, over time, by building beautiful buildings under the guidance of other master masons. Slowly, as they became adept, they would add their own touch and creativity to the new projects that they undertook. Does it sound familiar to how modern-day software are built?</p><p>Smart architects keep building their checklist from various projects. And when they apply those principles in new projects other architects and developers pick them up.</p><p><strong>CLARITY OF COMMUNICATION TO BUSINESS &amp; THE 8 HABITS</strong></p><p>Clarity of communication and understanding of business motivation is an important trait of a successful architect.</p><p>It really helps to use words like cost, efforts saving &amp; profitability rather than lines of code, design patterns &amp; more resources. But, that is a topic for a separate article “The words architects should never use in a business meeting”.</p><p>Right now, we are talking about ways to improve maintainability when dealing with developers, code and everyday development stuff. The habits that can save your company 50% cost and efforts overall.</p><p>Here are the 8 habits</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1003/1*g6PXt1q5jtbei6Ju9mkzBw.jpeg" /></figure><p><strong>The Art of Writing of Clean Code — It is in the name</strong></p><p>One of the most important criteria that must be fulfilled to obtain a maintainable software, in the long run, is to write clean and efficient code. There are some simple rules that lay down the foundation for writing a clean and efficient code.</p><p>Names are a very compelling way of stating the intent of your code to your fellow developers or whoever bumps into the beautiful lines who have written.</p><p>· Names should clearly reveal the intention of the code.</p><p>· Avoid misinformation. Codes should avoid using words that distort the true meaning of the code.</p><p>· Use names which are pronounceable and searchable. This reduces ambiguity within a team of developers who are working on the same project or anyone who reviews it from outside the team.</p><p>· Avoid encoding.</p><p>· Class names should be with the use of nouns and method names should be given with the use of verbs and not vice versa.</p><p>· One and the same concept in an application should have the same name, which in turn helps developers have a very clear understanding of the code.</p><p>All these will ensure that you have a uniform approach towards following a naming convention that automatically keeps the code clean and simple.</p><p>Efficient naming of code won’t single-handedly ensure that you have a clean code if the code gets duplicated.</p><p>The DRY (Don’t Repeat Yourself) principle, conceptualized by Any Hunt and Dave Thomas in the Pragmatic Programmer, talks about avoiding duplication of code at all cost. Structured programming, Aspect Oriented Programming, Component-Oriented Programming, are all, in part, strategies for eliminating duplication. Read more about the clean code here:</p><p><a href="https://medium.com/mindorks/how-to-write-clean-code-lessons-learnt-from-the-clean-code-robert-c-martin-9ffc7aef870c">How to write Clean Code? Lessons learned from “The Clean Code” — Robert C. Martin</a></p><p><a href="https://hackernoon.com/how-to-write-clean-code-d557d998bb08">How to write Clean Code?</a></p><p><a href="https://www.investigatii.md/uploads/resurse/Clean_Code.pdf">Clean Code: A handbook for Agile Software Craftsmanship by Robert C. Martin.</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1003/1*Vvb8GuMTwqeShr6VpVzatA.jpeg" /></figure><p><strong>Use consistent terminology / ubiquitous language</strong></p><p>Consistent terminology or ubiquitous language as termed by Eric Evans for the concept of Domain Driven Design (DDD) introduces the idea of a shared common vocabulary, that the entire team shares when discussing software. For example, a scenario where a ride-hailing app wants to add a coupon box in the checkout flow for customers to avail some discounts. If two separate words like ‘coupons’ and ‘discounts’ are used to communicate the same concept across the code structure, there will be confusions within the team and for the person who will review and approve the project.</p><p>This can be avoided by adopting only one name for every concept to have a clear idea. Ubiquitous language highlights the practice of creating a glossary which is a document that tracks your team’s language. This will be the document of all the terminologies, with its definitions that your team uses to write their code.</p><p>To have a more detailed understanding of this approach, you can refer to this <a href="https://blog.carbonfive.com/2016/10/04/ubiquitous-language-the-joy-of-naming/">article</a> or refer to <a href="https://www.amazon.com/Domain-Driven-Design-Tackling-Complexity-Software/dp/0321125215/ref=sr_1_2?crid=15N3IJ9V5BX2Q&amp;keywords=domain+driven+design&amp;qid=1550229221&amp;s=gateway&amp;sprefix=domain+dri%2Caps%2C436&amp;sr=8-2">Domain Driven Design</a>, an awesome book by Eric Evans.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1003/1*dNNeHgW2yRPmphIbcYai0Q.jpeg" /></figure><p><strong>Writing maintainable functions — SRP</strong></p><p>The first thing that one should keep in mind while creating functions is that it should be as small as possible without affecting the functionality. The secret to writing an effective and small function is to follow the <em>Single Responsibility Principle</em> where one function will have only one objective to fulfill.</p><p>Simplifying the functions further for better maintainability will need the developers to adhere to the necessary number of arguments which ideally should be zero, followed by one, and closely by two. Three arguments for a function should be avoided at all cost.</p><p>Functions should have a descriptive name clearly stating the function that it fulfills and last but not the least, there should be Command Query Separation where functions should either do something or answer something, but not both. Adopting these ideas in creating an effective function will take you to one more step towards a maintainable software.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1003/1*1Ipwb6c6RGjQPMhSpLe0jw.jpeg" /></figure><p><strong>Comments in a clean code — you don’t need to prove your code</strong></p><p>Counter to the popular wisdom on writing comments, comments should be written only if it is a critical necessity or has been specifically asked by a domain expert. Otherwise, it is highly advisable to leave them out. A clean code has the capability to clarify the intent without the need for comments. If your code needs comments to prove it’s flow, then you are doing something wrong.</p><p>At the same time, there are a few good comments which are sometimes necessary or beneficial or is specifically asked for. These could be Legal comments, Informative Comments, Explanation of Intent, Clarifications, Warning of Consequences, etc.</p><p>Refer to the link or the book to understand the impact of comments on the code. It is an eye-opener.</p><p><a href="https://medium.com/mindorks/how-to-write-clean-code-lessons-learnt-from-the-clean-code-robert-c-martin-9ffc7aef870c">How to write clean code? Lessons learned from “The Clean Code” — Robert C. Martin</a></p><p><a href="https://www.investigatii.md/uploads/resurse/Clean_Code.pdf">Clean Code: A handbook for Agile Software Craftsmanship by Robert C. Martin.</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1003/1*jDFWYXpb2BnFl02JJePZtw.jpeg" /></figure><p><strong>Documentation — Document specifications and knowledge base</strong></p><p>Truth is not in the documentation, it is in the code.</p><p>Then question is — why document?</p><p>The primary aim of documentation should be to write down why certain decisions were made during the software development cycle. This is knowledge documentation.</p><p>The other practical aim is to provide an environment, business rules, debugging, standards and usage specification to developers so that they can easily understand how the solution is designed.</p><p>When these two aims are considered, documentation becomes an important artifact during maintenance and knowledge transfer stages. But if documentation is taken up as a formality so that customer doesn’t penalize you, then you are going the ugly route of creating a mess.</p><p>Here are certain types of documentation that must be made available to developers</p><p>· <strong>Server environment documentation</strong> provides the server specifications in which the software runs. It helps in setting up new environments for the software when the need arises.</p><p>· <strong>Business rules</strong> documentation helps teams adapt quickly to the new business requirements of the software. Really what should be captured in this documentation besides the rules themselves, is the “why” of rules.</p><p>· <strong>Database documentation</strong> will help in bringing required additions to the software, help in the modification of the structure, add indexes and keys and make it much easier to control and debug.</p><p>· <strong>Troubleshooting</strong> documentation helps in noting down the type and severity of an error and formulate a fix for it. It should capture the motivation behind the fixes.</p><p>· <strong>Installation and configuration</strong> documentation to help developers to set up new or additional application environments.</p><p>· <strong>Code documentation</strong> helps to explain classes, methods, parameters, possible errors, etc.</p><p>There are various tools which will help you take care of software documentation. They take care of documentation at various stages of the software lifecycle like end-user documentation, requirements documentation, software architecture documentation, API documentation, etc. Some of the well-known documentation tools are Swagger, Madcap Flare, Jira, Trello, TestRail.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1003/1*8dF2VUNFUaAe0XNVoPBc3Q.jpeg" /></figure><p><strong>Code Review</strong></p><p>A more formal review environment involves developers reviewing code line by line to find errors. This is mostly carried out through meetings, using printed copies of the code and are extremely thorough.</p><p>In an informal setting, the original developer of the code walks through the code and explains each aspect to other developer/developers to convey the reason for the specific implementation.</p><p>Another very effective method of code reviews is Pair Programming, where the code is reviewed by another developer as it is written rather than reviewing it after the development has been done. One of the developers writes the code while the other acts as an <em>observer </em>or <em>navigator</em> who reviews each line of code as it is typed in, and they switch roles frequently. This if implemented will allow the observer to consider the quality of the code written, check for errors and enhance the maintainability of the software.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1003/1*KAGeXK29zFLTET2HFaVggg.jpeg" /></figure><p><strong>Continuous Integration</strong></p><p>Continuous Integration empowers you to test each modification or change a developer introduces to the codebase automatically and immediately as it occurs. Throughout an automation process, continuous integration eradicates manual deployment that has human errors.</p><p>Automation of the self-testing build based on set criteria eliminates the need for human intervention. This facilitates the reduction of labor on redundant activities, liberating people to engage in higher order work.</p><p>Continuous Integration eventually boils down to some habits that your team should establish within them.</p><p>· Commitment to daily testing.</p><p>· Narrow margin between the production environment and development environment.</p><p>· Fixing all broken builds. You must fix all the issues in the current development phase before moving onto the next.</p><p>One approach of development that particularly adopts the principle of Continuous Integration is Agile Software Development. Agile development teams generally take Continuous Integration very seriously.</p><p>There are tools in the market like Jenkins, TeamCity, Travis CI, Bamboo, Gitlab CI, Codeship, Circle CI, etc. which will take care of your Continuous Integration needs.</p><p>To understand more about Continuous Integration, refer to this <a href="https://www.martinfowler.com/articles/continuousIntegration.html">description</a> by Martin Fowler.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1003/1*gZ6vj4McBcWpZHI5nXGoWg.jpeg" /></figure><p><strong>Test, test, test &amp; automate</strong></p><p>Adopting the approach of manual testing only works if the project is significantly small. As the complexity increases there are possibilities of mistakes, especially when the application contains hundreds of lines of code.</p><p>This is where Automated Testing comes into the picture. It can run throughout or any time of the day thus reducing manual testing drastically, enabling developers to focus on project priorities and saves time and money for the organization in the long run.</p><p>This approach also fits well with the Continuous Integration development practices. It increases efficiency in bug detection, reusability, better reporting, optimum utilization of resources, all contributing to a strong maintainable software.</p><p>Test Driven Development is one system of development which ingrains the idea the Automated Testing in its practice. For a better understanding of TDD, refer to this <a href="https://medium.freecodecamp.org/test-driven-development-what-it-is-and-what-it-is-not-41fa6bca02a2">article</a>.</p><p>There are tools in the market that will take care of your automation when it comes to regular testing viz. Selenium, TestingWhiz, TestComplete, Ranorex, Telerix TestStudio, WatiN, etc.</p><p><strong>A final note</strong></p><p>Developing a maintainable software for the whole life cycle of a software is a difficult task, requiring continuous dedication and awareness.</p><p>These 8 ways that we discussed in this article will give you and your team a roadmap for achieving the goal of maintainable software. Again, business motivation should be clear. If you don’t understand it yet, take our word for it that there is a huge revenue impact when you make your software maintainable.</p><p>So, should you feel ubiquitous language is too simple a thing to pay attention to, think again. There is business impact associated with it in the form of maintainability.</p><p>Certain architectural patterns can help you create maintainable code more easily.</p><p>In our next article, we will talk about important “Architectural Patterns” which make it very easy for you to link the discipline of maintainability with code quality and speed.</p><p><strong>References:</strong></p><p><a href="https://www.toptal.com/front-end/frontend-clean-code-guide">https://www.toptal.com/front-end/frontend-clean-code-guide</a></p><p><a href="https://medium.com/mindorks/how-to-write-clean-code-lessons-learnt-from-the-clean-code-robert-c-martin-9ffc7aef870c">https://medium.com/mindorks/how-to-write-clean-code-lessons-learnt-from-the-clean-code-robert-c-martin-9ffc7aef870c</a></p><p><a href="https://hackernoon.com/how-to-write-clean-code-d557d998bb08">https://hackernoon.com/how-to-write-clean-code-d557d998bb08</a></p><p><a href="https://blog.carbonfive.com/2016/10/04/ubiquitous-language-the-joy-of-naming/">https://blog.carbonfive.com/2016/10/04/ubiquitous-language-the-joy-of-naming/</a></p><p><a href="https://www.codingdojo.com/blog/clean-code-techniques">https://www.codingdojo.com/blog/clean-code-techniques</a></p><p><a href="https://www.todaysoftmag.com/article/1071/clean-code-functions">https://www.todaysoftmag.com/article/1071/clean-code-functions</a></p><p><a href="https://filtered.com/blog/post/project-management/the-importance-of-documentation-in-software-development">https://filtered.com/blog/post/project-management/the-importance-of-documentation-in-software-development</a></p><p><a href="https://www.controldesign.com/articles/2013/document-document-document-for-maintainability/">https://www.controldesign.com/articles/2013/document-document-document-for-maintainability/</a></p><p><a href="https://stepshot.net/21-software-documentation-tools-for-every-stage-of-project-implementation/">https://stepshot.net/21-software-documentation-tools-for-every-stage-of-project-implementation/</a></p><p><a href="https://resources.collab.net/agile-101/continuous-integration">https://resources.collab.net/agile-101/continuous-integration</a></p><p><a href="https://blog.getty.io/importance-of-continuous-integration-on-software-development-30ab74c61c1">https://blog.getty.io/importance-of-continuous-integration-on-software-development-30ab74c61c1</a></p><p><a href="https://code-maze.com/top-8-continuous-integration-tools/">https://code-maze.com/top-8-continuous-integration-tools/</a></p><p><a href="https://www.martinfowler.com/articles/continuousIntegration.html">https://www.martinfowler.com/articles/continuousIntegration.html</a></p><p><a href="https://dzone.com/articles/top-10-automated-software-testing-tools">https://dzone.com/articles/top-10-automated-software-testing-tools</a></p><p><a href="https://searchsoftwarequality.techtarget.com/definition/automated-software-testing">https://searchsoftwarequality.techtarget.com/definition/automated-software-testing</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e9d56abcbe47" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Topic: Software Maintainability Checklist for Software Architects]]></title>
            <link>https://medium.com/hackernoon/topic-software-maintainability-checklist-for-software-architects-44527ae5f2af?source=rss-1a5eb25a7718------2</link>
            <guid isPermaLink="false">https://medium.com/p/44527ae5f2af</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[clean-code]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[maintainability]]></category>
            <dc:creator><![CDATA[FlexBase]]></dc:creator>
            <pubDate>Tue, 09 Apr 2019 06:37:21 GMT</pubDate>
            <atom:updated>2019-04-09T06:37:21.091Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Maintainability maketh a software great!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1003/1*kMwQ2qHU-CnoXCADza6dvg.jpeg" /></figure><p>A software will only be useful and purposeful if it passes the test of time and is functional for as long as the business decides. This is achieved when <strong>‘maintainability’</strong> is ingrained in software design.</p><p>So, what is maintainability?</p><p>It is the ability of a software system to support changes, be adaptable to the environment, and have the quality of quick repairability in case of a failure or downtime.</p><p>To say that a software is maintainable is to say it fulfills the quality attributes of modifiability, extensibility, reliability, and robustness, in their true sense. In addition, the software has documentation and enterprise design in place that makes it easy to understand for a person who is not familiar with it.</p><p>Why a checklist on maintainability? As an architect, if you have this checklist, it will serve as a handy tool to pre-empt situations which, otherwise, would have caught you off-guard. The checklist will help you have conclusive conversations with business and clients on product quality and timeliness.</p><p><strong>4 types of maintenance</strong></p><p>Before we dive into the checklist you must understand the 4 types of maintenance:</p><p>1. Adaptive Maintenance — The system needs to adapt to the changing technological environment or landscape (hardware, operating system or the platform). This aspect puts a demand on the design of the software itself. If you are dealing with COTS, then adaptive maintenance is something you need to perform regularly.</p><p>2. Corrective maintenance- If some bugs or issues occur within the software or if there is any failure, necessary corrective actions should be easy to initiate. Similarly, any correction/code change should not lead to the failure of any other part of the software. Here design patterns, loose coupling, and quality of code are the main concern.</p><p>3. Perfective Maintenance- It deals with making functional enhancements to the system in addition to the existing features as per user requirements or with an intention of continuous improvement. This is not based on the discovery of any faults but with the concept of continual improvement. Perfective maintenance is dependent on your contract and has an investment/expense implication.</p><p>4. Preventive Maintenance — It deals with the activities that are undertaken to prevent the occurrence of errors or faults.</p><p>For a more detailed take on the 4 types of software maintenance, read this beautiful <a href="https://bit.ly/2NNYe3t">article</a> by Jim Hayes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1003/1*c8FIOI-q6fHwFlPsM-sRBg.jpeg" /></figure><p><strong>Convincing business on maintainability is easy</strong></p><p>It needs additional effort to improve the maintainability of the software. But it is also understood, if maintainability is not addressed early on it can eventually lead to high TCO across the lifecycle of the software. Rather, in some big projects without addressing maintainability, you are more vulnerable to hitting a big-ball-of-mud scenario early in the development cycle itself.</p><p>So, it becomes significantly important to provide due recognition and respect for this attribute. It is no news that many software projects suffer &amp; fail when they don’t pay attention to non-functional requirements (NFRs). Often architects find it difficult to convince business folks to pay attention to NFRs.</p><p>This is where maintainability as a concept helps you. Maintainability is a quality attribute, that provides a measurable business &amp; technical framework to architects, using which they can communicate to clients and business folks the value of clean code and non-functional requirements. If you can demonstrate the impact of certain decisions in terms of the maintainability of software, you will have the attention of the business.</p><p><strong>Maintainability is made up of this …</strong></p><p>To understand this further let us discuss a bit about the sub-NFRs that constitute maintainability. One of the most important characteristics of maintainable software is <strong>‘Adaptability’</strong>. It is the extent to which a software system adapts to change in its environment. An adaptable software system can tolerate changes in its environment without external intervention. It would ensure that developers would not have to spend weeks writing migration or interface code. Adapting to a changing environment would be an easy and fast process. So, if your application in the future is required to talk to other systems or needs to provide reliability in a fast-changing technology landscape, then make design decisions that make your software adaptable.</p><p>Another characteristic that gives a clear indication of a maintainable software is its <strong>‘Modularity’</strong>. Measure how decoupled is the code. Is there good documentation of the design? Can changes &amp; fixes be done in the code without impacting the other parts of the software severely? Think about reducing regression issues.</p><p>Another indicator of maintainability is <strong>‘Performance’</strong>. If the performance is as per the expectations or beyond, it shows that the software was built with good design principles in mind.</p><p>To get an idea about all the characteristics that symbolize a maintainable software, keep the checklist below handy.</p><p>If you go by this checklist or let your customers/business teams agree on it, it becomes easier to lay emphasis on maintainability as an important quality attribute.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1003/1*_b3AUbY71djzLt2KFNWm_Q.jpeg" /></figure><p><strong>The maintainability checklist:</strong></p><p>· Does your software need to have a high level of performance?</p><p>· Will the number of users rises over a period of time?</p><p>· Will rise in the number of user’s impact performance?</p><p>· Will the software be communicating with other third-party software and legacy systems?</p><p>· Are there competing technology environments?</p><p>· Are you aware of rising technology trends in OS, hardware, and languages?</p><p>· Is the requirement modular enough to create a modular architectural design?</p><p>· Is the code that is being written easy to debug?</p><p>· Do developers understand the commenting and documentation standards that must be followed?</p><p>· Is there enough documentation and relevant comments in the code, so that it is easy for a new developer to understand?</p><p>· Is there a low level of code coupling?</p><p>· Do you know how much time you will take to create new interfaces?</p><p>· Does your development team understand the coding standards that they have to follow?</p><p>· Do you have software quality testing in place?</p><p>· Do you have a continuous delivery model?</p><p>The above Checklist establishes maintainability as a critical contributor to optimal software. This will help in taking an organized approach towards adopting maintainability and getting the attention of decision makers. Getting answers to these questions helps you estimate for NFRs.</p><p>To know how some of the best architects have been solving maintainability problem, check out our next article on the maintainability series which talks about ‘8 habits of successful architects to create easy to maintain software’.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=44527ae5f2af" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/topic-software-maintainability-checklist-for-software-architects-44527ae5f2af">Topic: Software Maintainability Checklist for Software Architects</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Scalability — Think in terms of TCO]]></title>
            <link>https://medium.com/hackernoon/scalability-think-in-terms-of-tco-73cfb0a99137?source=rss-1a5eb25a7718------2</link>
            <guid isPermaLink="false">https://medium.com/p/73cfb0a99137</guid>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[scalability]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software]]></category>
            <dc:creator><![CDATA[FlexBase]]></dc:creator>
            <pubDate>Mon, 01 Apr 2019 09:51:48 GMT</pubDate>
            <atom:updated>2019-07-19T06:37:29.269Z</atom:updated>
            <content:encoded><![CDATA[<h3>Scalability — Think in terms of TCO</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/589/1*TlP2MYsE1mls0FIM3zuJ6A.png" /></figure><p>A system that has an ability to easily scale resources to meet the increasing workload without affecting the performance is known as a scalable system. The workload could refer to anything from an increase in users, usage, storage or number of transactions.</p><p>To make an easy to scale system, it is crucial to have an evolutionary way of thinking about software development cycle. This means the software architect should focus on designing a scalable software architecture from the early phase of the product life cycle.</p><p>Why? Because it will impact the Total Cost of Ownership (TCO) of your software in a big way. A late-stage consideration of improving scalability requires rewriting a big chunk of application code. And with that there is a big possibility of regression issues creeping in.</p><p>This blog provides vantage points to understand the best practices in achieving ease of scalability. We present a checklist on scalability that architects can maintain. You will find it handy and useful in business meetings where requirements &amp; efforts get discussed.</p><p>Before you look at the checklist (which you can do by scrolling down), you must understand the kind of scalability that we are talking about. Let’s peep into client requirements that you will be required to scale for.</p><h3><strong>Understanding requirements for scalability</strong></h3><p>First, let’s talk about the popular version of scalability — dynamic scalability. A dynamically scalable system has the ability to handle an extra load by scaling within a minute or no notice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/539/1*CWjeIA83OYutIbVXLnYRNg.png" /></figure><p>Think of Uber. If your app shows some error during peak booking hours, you expect that if you close the app and open it again, the problem should be gone. A dynamically scalable system should be able to handle loads at that speed.</p><p>Or, think of Netflix. The load on their servers increases substantially during weekends. So, their systems should be able to distribute and respond to the extra load during weekends dynamically.</p><p>On the other hand, in Enterprise Applications the scalability requirements might not be so desperate or fast-changing. Yet you might be required to design dynamically scalable modules of the application. For example, think of a CRM or a salary processing system during a month-end scenario. In these systems, usage or the number of transactions can increase drastically during month-ends. Sometimes up to 10x the average load. In this case you will need to design these systems for a sudden rise in usage over month-ends.</p><p>Typically, in enterprise applications, scalability becomes a concern after quite some time when the number of users, transactions or the memory records increase considerably, and the performance bottlenecks start appearing in the usage of the application regularly. Whether you will hit these bottlenecks in 6 months or 3 years depends on how fast the business grows.</p><p>This means Enterprise Applications architects must pay close attention to coding standards and design patterns which will impact the ease of scaling of the application in the future.</p><p>To understand how you can do that, you should understand two types of scaling — Vertical and Horizontal.</p><h3><strong>Design for Horizontal Scaling</strong></h3><p><strong>What is Vertical Scaling? </strong>The other term used is “scaling up”. When you scale a system vertically you increase the power of the current hardware. This can mean greater memory, faster storage or more advanced processors. It is more convenient among the two methods since change in hardware capcity requires very little change at the software level if any.</p><p>For handling a month-end load consider a vertically scaled set up.</p><p><strong>What is Horizontal Scaling? </strong>It is also known as “scaling out”, where you increase the number of servers to balance the load. In this one, software adopts to scalability not by adding powerful hardware but by spreading the workload across new set-ups. Nevertheless, scaling-out comes with the price where it adds more complexity to the system. Moreover, having multiple servers require general administrative tasks such as security, monitoring, data, and backups.</p><p>Consider horizontal scaling when current average performance hits a dead-end.</p><h3><strong>Best practices to build a scalable system</strong></h3><p>One last hop before we craft the checklist. Let’s first look at some of the best practices that architects use for designing easy to scale systems.</p><p><strong>Loose coupling</strong>: Building loosely coupled code enables an application to scale much faster at less cost. In such a design, the bottlenecks can be easily recognized. You can increase the capacity of one component without disturbing the overall application. In addition, you are not haunted by regression issues when you undertake to scale.</p><p><strong>Asynchronous components:</strong> It is important to carefully analyze the application design to determine whether to keep components synchronous or asynchronous. Building asynchronous components make scaling easy.</p><p><strong>Cacheing:</strong> While designing scalable system it is important to offload the database as much as possible. Cacheing helps to achieve this objective especially for retrieving information from the database in read-only mode. It is advisable to use in-memory cache rather than on-disk cache or relational database.</p><p><strong>High Cohesion:</strong> A strong cohesion amid subsystems result in less round excursions since classes are logically grouped and reside in the same tiers. This can greatly reduce local and remote calls to complete a logical operation. This makes scaling easy.</p><p><strong>Decentralization:</strong> a Distributed system is a group of subsystems operating on independent servers. This ensures ease of high availability by increasing the number of servers.</p><p><strong>Position:</strong> Important components should be kept as close as together. For instance, it is less cumbersome to go through the content delivery network than to go through a load balancer, web server, and database for content retrieval.</p><p><strong>Lesser network chatter:</strong> Design network as untalkative as possible since network communications tend to be slower as compared to in-memory ones.</p><p><strong>One resource one function:</strong> Make sure one resource caters to one function in case of multiple requests for the same resource. If you don’t do this, then, despite scaling the system, you will be bogged down by the slow performance.</p><h3><strong>The Checklist</strong></h3><p>Finally, now, what are the points you must keep in mind when undertaking a new application development project? We have prepared this short checklist for architects when they are designing for scalability.</p><p>It will help you put good emphasis on scalability during business requirement gathering.</p><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><p><strong>Business requirements checklist</strong></p><p>→ Have you considered month-end scenarios?</p><p>→ How much will the load increase during month-ends or any other periodic business cycle?</p><p>→ Are there any directly stated scalability requirements from the client?</p><p>→ What is the estimated increase in the number of users or transactions in the next 6 months, 1 year, 2 years?</p><p><strong>Architecture design checklist</strong></p><p>→ Have you calculated the increase in usage, storage &amp; transactions requirement in the next 6 months, 1 year, 2 years?</p><p>→ Have you figured out processes which should be made asynchronous?</p><p>→ Have you considered all options to increase software performance?</p><p>→ Is your design optimized for frequent and crucial tasks?</p><p>→ Have you figured how often the system should use a cache?</p><p>→ Do you have a distributed system in place?</p><p>→ Do you have load balancing software in place?</p><p>→ Is the database scalable?</p><p>→ Does your architecture design enforce decoupling?</p><p><strong>Coding checklist</strong></p><p>→ Are you making sure the developers are strictly following the single responsibility principle?</p><p>→ Does your code review guideline include the single responsibility principle as an important check?</p><p>→ Are you developers following decoupling standards and design patterns?</p><p>→ Have you taken care of asynchronous processing?</p><p><strong>Testing checklist</strong></p><p>→ Can you simulate peak loads in test cases? Has the testing team considered test-cases with 5X or 10X increase in transaction/user load?</p><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><p>Have we missed anything? Are there any more critical points which should be included in this checklist? Write to us in the comments below.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=73cfb0a99137" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/scalability-think-in-terms-of-tco-73cfb0a99137">Scalability — Think in terms of TCO</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>