Technical Terms Every Founder Should Understand | SOLITAIRE INFOSYS
Request a Quote !

Request a Quote !

Request a Quote !

Blogs

Technical Terms Every Founder Should Understand | SOLITAIRE INFOSYSTEMS

  • By: admin
  • date: Aug 29, 2022
Blog Image

We frequently meet founders who are starting their first business. While they are flawless in terms of their excitement, desire, and determination to achieve, they occasionally fall short in their understanding of technical jargons and terminology that developers may use when communicating with them.

 At this stage, it can be difficult for founders to understand, and they are forced to pick between the devil and the deep blue sea—whether to nod along or to ask and appear silly.

So, don’t worry, I’ve put together a handy reference for all the terminology that developers regularly use. This is meant to help founders understand and communicate more effectively.

 1.Frontend/Backend/Database/Architecture/Hosting/APIs

A platform is typically composed of two pieces.

The interface with which users interact is known as the front end. The items you see are the front end, just like on a Facebook page.

The backend refers to the components that operate behind the scenes, such as the database, logic, and hosting.

So, what exactly are database and hosting?

A database is a record of all data that has been organised. This would typically include user profiles, user data such as posts and photographs, and varying degrees of access.

Hosting is the process of putting your website or app on a server and making it accessible via the internet.

The architecture is formed by combining all of the preceding elements. Software architecture is the assembly of various systems—frontend, backend, database, and so on—and their integration.

APIs are the interfaces that allow two pieces of software or various softwares to communicate with one another. When you access Facebook, the backend and frontend are linked via APIs, as are when you utilise the platform to send messages or conduct a transaction involving Facebook and another site.

 2. Cloud/Internet Protocol/Deployment/Servers

As previously said, the application is hosted on servers. Servers are simply computers, however rather of purchasing your own machines to operate as a server, you rent them from firms such as Amazon, Google, and others. These corporations have invested in assembling millions of such machines, which you may hire on a pay-as-you-go basis.

Because you do not own these equipment, this type of hosting is known as cloud hosting.

IP addresses are how your website is identified on the internet. To reach a website, we often type in its address; yet, on the internet, these names have unique addresses in the form of a combination of digits.

The IP address of Google is 216.58.217.206.

If you copy and paste this number into your browser, you’ll be able to access Google.com.

When you host your website (send it to a server), you are assigned an IP address. It’s similar to a street address. IP addresses can be found using your Windows (Open command prompt and enter in “tracert”) or Mac (Go in spotlight>Network Utility> Double Click and to traceroute), as well as websites such as Uptrends.

 Once your platform is complete, you will need two servers: staging and live.

The team shares the staging server link and uses it for testing. When new changes are made, they are incorporated into the software stored on the staging server. This manner, the platform can be tested by everyone on the team. Once the modifications have been reviewed and tested, they are added to the live platform, allowing your users to begin using the new features.

When the Facebook team creates a new feature, it is initially internally tested on the staging server. If bugs are discovered, they are fixed. This cycle continues until the team determines that no bugs exist, at which point the new module is uploaded to the existing platform and people all over the world can utilise the new features.

 You may have noticed that Facebook deploys to a small group of individuals first, then to the rest of the world. This is achievable due to the staggered deployment strategy for both mobile apps and the web. This is extremely beneficial when you have a large audience from all over the world.

 3. Query/Authorization/Authorization/Authentication

 A query is a method of retrieving data from a database. Because your database contains a large amount of information. Querying is the formal method through which the system obtains data from a database.

The system is constantly in need of data. When you enter Facebook, for example, the system checks the database if there is a person with the login “XX” and the password “YY.” Show his page if the same is true.

That is how you perceive your page.

Similarly, every action you take, such as seeing a photo, liking or commenting on it, or even deleting it, is a query to the database.

Authorization is the process of granting specific authorization to a user, whereas authentication is the process of recognising the person. Authentication comes after authorization. When you as a user can access some things on Facebook but not their backend or other things, this is due to permission. Authentication is the process of identifying you using your username and password.

4. Monitoring/Analytics/User Behaviour

Keeping logs of system actions is what logging is all about. Logs are useful for determining what actions occurred in the systems and when, as well as identifying any unexpected behaviour during any of the actions. Logging is extremely useful for determining the root cause of crashes and issues.

Conclusion :

So these are the various things that will be valuable to you at various stages of your product journey. Furthermore, if you come across any terminology that you don’t understand, don’t be afraid to ask. Always ask questions and use Google.

 

About the Author

Comments