Skip to main content

Part 1 - Overengineering of a cloud application

By
N-tier architecture is seen nowadays as an old. People tends to migrate to event-base or microservice architecture. It's very common to see people that decide an architecture based on the market trends, ignoring the requirements, business needs and budget.

When you combine this with Azure (cloud in general) you will end up easily with a microservice architecture that combines messaging systems and event-driven architectures. Of course, N-tier application has a lot of disadvantages, but when you have a simple web application, there is no sense to create a complex unicorn that will survive for 100 years.

I was shocked to review a solution that was deployed in Azure 2 months ago, that from architures point of view was beautiful, but from the running and development costs become a nightmare.
I will not go in details of the business requirements, but imagine a system that needs to display some static information, allow users to upload small CSV files that are consolidated in a reporting system. Figures:

  • Under 200 users worldwide
  • Concurrency level is 10% (20 users online simultan)
  • Less than 15 CSV uploaded in total per day
  • Basic reporting functionality
  • Current DB size 150MB (2M reporting entries)
  • DB forecast for next 3 years is 1GB (20-25M reporting entries)
  • CSV has up to 1000 entries (maximum 10 columns)
For a system like this, it was a delight to discover a microservice solution in the backed hosted on a dedicated cluster that communicates between each other using Azure Service Bus. The front-end was a SPA with a nice REST API. Behind this, there was an Hadoop Cluster that would process the CSV files, extracting points for charts, pushing the results in a DocumentDB. User management was done using a system hosted in Azure SQL Database. 
There were also some other system involved, but this are the main components.

I don't know what is you opinion about this kind of system. Personally I like how it was design, it's extremely scalable and can process and manage high loads. In the same time, I take a look on the requirements and I ask myself 'WHY?!'.

My main goal was to reduce running costs and complexity of the project with a minimal impact. If you want to find out what was our proposed solution you should check the blog tomorrow.

Part 2 - The solution
Labels:

Comments

  1. UnknownJune 12, 2017 at 11:50 AM

    I was interested to hear about your proposed solution but cannot find it on this blog

    ReplyDelete
  2. tudor_turcuJune 12, 2017 at 1:21 PM

    wow.. All this should fit easily on a single server, not even a large one.. :)

    ReplyDelete

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

By
After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(...
Post a Comment
Read more

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

By
Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see...
8 comments
Read more

Navigating Cloud Strategy after Azure Central US Region Outage

By
 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provi...
Post a Comment
Read more