What to consider when choosing teck stack for your project

00:00 → 00:02

When building new digital product,

00:02 → 00:06

selecting technology stack may be a daunting task.

00:06 → 00:10

There's plethora of options to choose from, but don't worry.

00:10 → 00:12

Merixstudio has you covered.

00:12 → 00:17

Almost any technology is usable or viable in most of cases.

00:17 → 00:20

So I have four tips for you today to see if the technology

00:20 → 00:23

is best fit for your needs and requirements.

00:23 → 00:27

First thing you might want to consider is the purpose.

00:27 → 00:29

What do you want to build?

00:29 → 00:33

Is it a prototype which will allow you to quickly

00:33 → 00:37

verify your business assumptions?

00:37 → 00:40

This is where you would like to choose the technology

00:40 → 00:44

that will allow you to create some kind of solution very rapidly.

00:44 → 00:48

And that will allow you to verify your assumptions on the market.

00:48 → 00:52

On the other hand, if you want to build already working

00:52 → 00:56

application that you are not looking to

00:56 → 01:00

scrap and rebuild from scratch to meet different kind of

01:00 → 01:03

goals, you will want to choose different

01:03 → 01:06

technology, resilient one, the one that will allow you to

01:06 → 01:09

build maybe even enterprise class software.

01:09 → 01:14

Second thing you might want to consider is the use case.

01:14 → 01:17

Whether you are building application that will highly

01:17 → 01:20

rely on machine learning or data science,

01:20 → 01:23

then you would like to choose Python or some of the

01:23 → 01:25

frameworks working with Python.

01:25 → 01:27

Or maybe you are looking to build more general general

01:27 → 01:29

purpose platform.

01:29 → 01:31

If that is the case,

01:31 → 01:36

you may choose from different languages as PHP, Python, or Ruby.

01:36 → 01:41

And maybe there were there will be some small details

01:41 → 01:45

that will gear it towards one or another technology.

01:45 → 01:47

Third thing is architecture.

01:47 → 01:52

In most cases, new applications are built as monoliths.

01:52 → 01:56

Meaning, there are different functionalities under one application.

01:56 → 02:00

If you know you want to build huge scale application

02:00 → 02:04

or service that will need very different

02:04 → 02:08

functionalities on different ends of of that

02:08 → 02:11

solution, you might want to consider going with

02:11 → 02:12

microservices.

02:12 → 02:17

Then your choices will be regarding specific pieces of

02:17 → 02:20

the application, specific functionalities.

02:20 → 02:23

You will have multiple technology stacks for different purposes.

02:23 → 02:26

And lastly, it's the popularity.

02:26 → 02:29

Whether the language or technology is popular will

02:29 → 02:33

allow you to have access to different

02:33 → 02:36

specialists who know this technology.

02:36 → 02:38

What is more also very important regarding the

02:38 → 02:43

popularity is the use cases that somebody has already used

02:43 → 02:47

that technology for similar purpose.

02:47 → 02:52

There are many libraries that allow you to build different

02:52 → 02:56

aspects of the applications, and there is the community

02:56 → 03:00

behind a technology or solution that will allow

03:00 → 03:03

you to get any help if you stuck.

03:03 → 03:06

You may also consider building a proof of concept.

03:06 → 03:09

Sometimes creating a prototype and measuring

03:09 → 03:15

specific parameters will give you most answers to your questions.

03:15 → 03:19

Establish the requirements, the goals you want to meet,

03:19 → 03:23

create a solution that will allow you to do that and measure.

03:23 → 03:25

This is what we do in Merixstudio.

03:25 → 03:29

So you may come over to us and let's discuss the details

03:29 → 03:30

of your project.