MBaaS vs. custom backend: what to choose? | IT Depends

00:00 → 00:03

If you have been thinking about developing a mobile app,

00:03 → 00:06

you must have come across mobile backend as a service,

00:06 → 00:10

which literally translates to using a ready made backend.

00:10 → 00:14

But is it true that it works better than the good old custom backend?

00:14 → 00:16

Well, it depends.

00:21 → 00:24

Let's start with mobile backend as a service.

00:24 → 00:26

What are the advantages and limitations?

00:26 → 00:29

Reduced but unpredictable costs.

00:29 → 00:33

This solution is tempting for early stage startups and small

00:33 → 00:36

projects mainly because of the low cost implementation.

00:36 → 00:41

You simply save money and time without creating a back end from scratch.

00:41 → 00:42

What's even better,

00:42 → 00:45

it comes with many additional services that you typically

00:45 → 00:46

have to pay for.

00:46 → 00:48

It seems like a win win, doesn't it?

00:48 → 00:50

Regardless of the backend solution,

00:50 → 00:55

the increase in user traffic may have a painful impact on your wallet.

00:55 → 00:58

You have to be especially careful about this in the case

00:58 → 01:02

of backend as a service since improper use of this

01:02 → 01:07

service's resources can speaking directly burden you financially.

01:07 → 01:10

Limited amount of functionalities in one bundle

01:10 → 01:12

controlled by the vendor.

01:12 → 01:16

Unfortunately, the increase in costs may not translate into

01:16 → 01:18

future development of the app.

01:18 → 01:22

Backend providers usually have a specific set of features

01:22 → 01:26

that are compatible with each other and ready to be included.

01:26 → 01:29

This means that as your application grows,

01:29 → 01:31

you're limited to such a list only.

01:31 → 01:34

This isn't a deal breaker for small projects.

01:34 → 01:38

However, if you plan to add new functionalities in the future,

01:38 → 01:41

it's worth looking for a service that will cover them

01:41 → 01:42

from day one.

01:42 → 01:46

At worst, you'll have to spend more time and money building a backend

01:46 → 01:48

that does not restrict you.

01:48 → 01:50

Shorter time to market.

01:50 → 01:52

Speaking of spending time and money,

01:52 → 01:55

time is the second most important resource that you can

01:55 → 01:58

save by choosing mobile back end as a service.

01:58 → 02:01

This means you can pay more attention to the frontend,

02:01 → 02:04

and the application itself will land on the market faster.

02:07 → 02:11

What if you can't find backend as a service that meets all the requirements?

02:11 → 02:13

Then you have to build the backend from scratch,

02:13 → 02:15

and here's what you need to consider.

02:15 → 02:20

It increases development costs but retains complete control over it.

02:20 → 02:21

At first glance,

02:21 → 02:25

it seems that a custom backend consumes more time and money.

02:25 → 02:28

First, you need to set up a development team for this.

02:28 → 02:31

Second, this team needs time to build it.

02:31 → 02:33

The truth is it might not be profitable for small

02:33 → 02:37

applications, but it is for larger long term projects.

02:37 → 02:41

As I mentioned before, the price of a mobile backend as a

02:41 → 02:45

service can increase overnight spinning the budget out of control.

02:45 → 02:48

You are in control though when you build the backend for

02:48 → 02:50

the application from scratch.

02:50 → 02:54

Controlled performance and sustainability due to owning the code base.

02:54 → 02:58

Another quite obvious difference is that you own the source code.

02:58 → 03:01

That gives you additional confidence that the application

03:01 → 03:05

is up to date and will stay that way as you take care of it yourself.

03:05 → 03:07

In the case of backend as a service,

03:07 → 03:11

our application works fine as long as the service itself

03:11 → 03:12

works okay.

03:12 → 03:15

Independence gives you complete control over the performance,

03:15 → 03:18

quality of the code, and its changes.

03:18 → 03:20

Unlimited customization.

03:20 → 03:23

There's another advantage associated with owning the code.

03:23 → 03:28

Your application is not limited in development to the list of functions.

03:28 → 03:32

Even if you can add your own scripts and functions in the

03:32 → 03:35

case of the back end as a service, sooner or later,

03:35 → 03:38

if you want to develop and scale your application with a

03:38 → 03:42

custom back end, the risks of hitting a wall is lower.

03:44 → 03:45

As you can see,

03:45 → 03:48

choosing the type of backend is more a long term decision

03:48 → 03:49

than you might think,

03:49 → 03:52

and you have to consider many factors when making it.

03:52 → 03:56

Is your application supposed to be huge or small?

03:56 → 03:59

Do you need to release it quickly to the market,

03:59 → 04:04

or do you have time and resources to refine this aspect yourself?

04:04 → 04:07

Can you put together a dedicated team to develop the

04:07 → 04:09

backend and its capabilities,

04:09 → 04:13

or is it enough for you to go and get a ready-made solution

04:13 → 04:16

with a predefined set of functionalities?

04:16 → 04:18

Both ways have pros and cons,

04:18 → 04:22

so the final decision depends on your specific needs.