Free your business growth with elastic software architecture

Radek Kamiński - March 20, 2019

Some time ago I was doing research in regards to the way how start-up projects are managed from a technical perspective, and I found an often problem - how to scale an application in satisfying time frame, without cross-cutting changes in the codebase?

Common business scenario

Let’s imagine a typical business case. A company wants to validate business idea very quickly and with a limited budget. They develop something called a Minimum Viable Product (in fact in many start-up projects it is Proof of Concept rather than MVP) and launch it in a cloud. On the one hand, the company believes in idea success and wants to provide as many features as possible, on the other hand, project management is focused on quick launch. This opposite approaches usually exclude setting some time aside for a long-term strategy preparation of the project’s growth, which is a ticking time bomb that may blow off when you’re least expecting. If the code architecture is not well-thought, your project may end up in a state when you cannot develop anything new or implement a functionality change at a sustainable pace.

What are the symptoms pointing to architectural problems? Let’s see some examples.

  • A simple improvement in the base code like changing the message text or updating configuration parameter requires launching the whole time-consuming release process.

  • Understanding what is going on in the code takes a lot of time due to a massive amount of code in the single standalone code unit.

  • Modules are tightly coupled, so it is a problem to make a change in one module without affecting the stability of the other dependant ones.

  • Configuring a new development environment is a challenge.

If some of the above symptoms are true in your case, it’s time to think about architecture transformation. Depending on how far you planned the transformation strategy it will be a more or less painful process for the project.

Beginning shape of an application

Let’s try to review an application for meals ordering. A company is about to launch an MVP version of its mobile app that allows interacting 2 actors:

  • Meal Providers upload their offers in the system

  • Customers order meals.

The typical scenario is to prepare an easily extendable and deployable monolithic application as shown in the picture below:

Basic one-node architecture

At this stage, we need to think about potential bottlenecks that may stop business growth in the first place. So far it won’t be development speed, as the code base is relatively simple in the early phase. An entirely possible scenario is related to an increasing number of Providers submitting their offers to the system first before Consumers will start coming drastically and searching through offers. It may lead to overconsumption of IOPS in DB, so the first potential bottleneck is related to performance.

We can quite easily scale the whole application vertically by buying more resources in the cloud, but scaling horizontally may be a challenge. For example, you must take care of session data sharing between nodes, load balancing algorithm, etc.

Another thing that may affect scalability a lot is the decision whether to use RDBMS or NoSQL for data storing. Consideration of one or another approach is a good candidate for a next article, however, having an ability to use a NoSQL solution gives usually better built-in mechanisms for scalability. If NoSQL is impossible to use we need to consider an architecture that allows overcoming this problem with RDBMS.

Architecture growth

One of the fastest solutions that solve mentioned above problem is to separate reads from writes. The idea is inspired by the CQRS pattern, unfortunately, implementing this pattern is time-consuming. What we can implement quickly, is to multiply our architecture and combine it by introducing HTTP aware Load Balancer, which redirects reads (GET method) to one node and writes (POST, PUT, DELETE, etc.) to another. To reduce the amount of work, we should locate all components in one data center initially - load balancing between different DCs is a bigger challenge. The bottom line of the solution is that now we have 2 mirrored databases.

Two-nodes architecture with separated reads from writes

Conclusion

As you can see we scaled our app without the need of re-building the code base, which should be a quick job. This way we gained extra time for architecture refactoring and rethinking the whole tech perspective. In my next articles, I’ll try to show you what would be the next steps of a possible transformation.

About the author

Radek Kamiński

Company Lead (broadly known as CEO)

Radosław is a software industry veteran with over 15 years of experience in the IT field. He has excellent knowledge and expertise in agile software development methods. Radosław focuses on building and nurturing self-organizing teams that focus on AI and Big Data solutions.
Personal experiences have encouraged him to implement transparency, open communication, shared responsibility, and a flat organizational structure at nexocode. A servant leader by nature, he's always keen to learn from others - often exchanging opinions with them on how things can be better done!

Find us on

Need help with implementing AI in your business?

Let's talk blue circle

This site uses cookies for analytical purposes.

Accept Privacy Policy

In the interests of your safety and to implement the principle of lawful, reliable and transparent processing of your personal data when using our services, we developed this document called the Privacy Policy. This document regulates the processing and protection of Users’ personal data in connection with their use of the Website and has been prepared by Nexocode.

To ensure the protection of Users' personal data, Nexocode applies appropriate organizational and technical solutions to prevent privacy breaches. Nexocode implements measures to ensure security at the level which ensures compliance with applicable Polish and European laws such as:

  1. Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation) (published in the Official Journal of the European Union L 119, p 1); Act of 10 May 2018 on personal data protection (published in the Journal of Laws of 2018, item 1000);
  2. Act of 18 July 2002 on providing services by electronic means;
  3. Telecommunications Law of 16 July 2004.

The Website is secured by the SSL protocol, which provides secure data transmission on the Internet.

1. Definitions

  1. User – a person that uses the Website, i.e. a natural person with full legal capacity, a legal person, or an organizational unit which is not a legal person to which specific provisions grant legal capacity.
  2. Nexocode – NEXOCODE sp. z o.o. with its registered office in Kraków, ul. Generała Henryka Kamieńskiego 51, 30-644 Kraków, entered into the Register of Entrepreneurs of the National Court Register kept by the District Court for Kraków-Śródmieście in Kraków, 11th Commercial Department of the National Court Register, under the KRS number: 0000686992, NIP: 6762533324.
  3. Website – website run by Nexocode, at the URL: nexocode.com whose content is available to authorized persons.
  4. Cookies – small files saved by the server on the User's computer, which the server can read when when the website is accessed from the computer.
  5. SSL protocol – a special standard for transmitting data on the Internet which unlike ordinary methods of data transmission encrypts data transmission.
  6. System log – the information that the User's computer transmits to the server which may contain various data (e.g. the user’s IP number), allowing to determine the approximate location where the connection came from.
  7. IP address – individual number which is usually assigned to every computer connected to the Internet. The IP number can be permanently associated with the computer (static) or assigned to a given connection (dynamic).
  8. GDPR – Regulation 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of individuals regarding the processing of personal data and onthe free transmission of such data, repealing Directive 95/46 / EC (General Data Protection Regulation).
  9. Personal data – information about an identified or identifiable natural person ("data subject"). An identifiable natural person is a person who can be directly or indirectly identified, in particular on the basis of identifiers such as name, identification number, location data, online identifiers or one or more specific factors determining the physical, physiological, genetic, mental, economic, cultural or social identity of a natural person.
  10. Processing – any operations performed on personal data, such as collecting, recording, storing, developing, modifying, sharing, and deleting, especially when performed in IT systems.

2. Cookies

The Website is secured by the SSL protocol, which provides secure data transmission on the Internet. The Website, in accordance with art. 173 of the Telecommunications Act of 16 July 2004 of the Republic of Poland, uses Cookies, i.e. data, in particular text files, stored on the User's end device.
Cookies are used to:

  1. improve user experience and facilitate navigation on the site;
  2. help to identify returning Users who access the website using the device on which Cookies were saved;
  3. creating statistics which help to understand how the Users use websites, which allows to improve their structure and content;
  4. adjusting the content of the Website pages to specific User’s preferences and optimizing the websites website experience to the each User's individual needs.

Cookies usually contain the name of the website from which they originate, their storage time on the end device and a unique number. On our Website, we use the following types of Cookies:

  • "Session" – cookie files stored on the User's end device until the Uses logs out, leaves the website or turns off the web browser;
  • "Persistent" – cookie files stored on the User's end device for the time specified in the Cookie file parameters or until they are deleted by the User;
  • "Performance" – cookies used specifically for gathering data on how visitors use a website to measure the performance of a website;
  • "Strictly necessary" – essential for browsing the website and using its features, such as accessing secure areas of the site;
  • "Functional" – cookies enabling remembering the settings selected by the User and personalizing the User interface;
  • "First-party" – cookies stored by the Website;
  • "Third-party" – cookies derived from a website other than the Website;
  • "Facebook cookies" – You should read Facebook cookies policy: https://www.facebook.com/policy/cookies
  • "Other Google cookies" – Refer to Google cookie policy: www.google.com/policies/technologies/types/

3. How System Logs work on the Website

User's activity on the Website, including the User’s Personal Data, is recorded in System Logs. The information collected in the Logs is processed primarily for purposes related to the provision of services, i.e. for the purposes of:

  • analytics – to improve the quality of services provided by us as part of the Website and adapt its functionalities to the needs of the Users. The legal basis for processing in this case is the legitimate interest of Nexocode consisting in analyzing Users' activities and their preferences;
  • fraud detection, identification and countering threats to stability and correct operation of the Website.

4. Cookie mechanism on the Website

Our site uses basic cookies that facilitate the use of its resources. Cookies contain useful information and are stored on the User's computer – our server can read them when connecting to this computer again. Most web browsers allow cookies to be stored on the User's end device by default. Each User can change their Cookie settings in the web browser settings menu: Google ChromeOpen the menu (click the three-dot icon in the upper right corner), Settings > Advanced. In the "Privacy and security" section, click the Content Settings button. In the "Cookies and site date" section you can change the following Cookie settings:

  • Deleting cookies,
  • Blocking cookies by default,
  • Default permission for cookies,
  • Saving Cookies and website data by default and clearing them when the browser is closed,
  • Specifying exceptions for Cookies for specific websites or domains

Internet Explorer 6.0 and 7.0
From the browser menu (upper right corner): Tools > Internet Options > Privacy, click the Sites button. Use the slider to set the desired level, confirm the change with the OK button.

Mozilla Firefox
browser menu: Tools > Options > Privacy and security. Activate the “Custom” field. From there, you can check a relevant field to decide whether or not to accept cookies.

Opera
Open the browser’s settings menu: Go to the Advanced section > Site Settings > Cookies and site data. From there, adjust the setting: Allow sites to save and read cookie data

Safari
In the Safari drop-down menu, select Preferences and click the Security icon.From there, select the desired security level in the "Accept cookies" area.

Disabling Cookies in your browser does not deprive you of access to the resources of the Website. Web browsers, by default, allow storing Cookies on the User's end device. Website Users can freely adjust cookie settings. The web browser allows you to delete cookies. It is also possible to automatically block cookies. Detailed information on this subject is provided in the help or documentation of the specific web browser used by the User. The User can decide not to receive Cookies by changing browser settings. However, disabling Cookies necessary for authentication, security or remembering User preferences may impact user experience, or even make the Website unusable.

5. Additional information

External links may be placed on the Website enabling Users to directly reach other website. Also, while using the Website, cookies may also be placed on the User’s device from other entities, in particular from third parties such as Google, in order to enable the use the functionalities of the Website integrated with these third parties. Each of such providers sets out the rules for the use of cookies in their privacy policy, so for security reasons we recommend that you read the privacy policy document before using these pages. We reserve the right to change this privacy policy at any time by publishing an updated version on our Website. After making the change, the privacy policy will be published on the page with a new date. For more information on the conditions of providing services, in particular the rules of using the Website, contracting, as well as the conditions of accessing content and using the Website, please refer to the the Website’s Terms and Conditions.

Nexocode Team