Name: オフラインファーストのデータ。ケビン・ドーランの「大きくなるために」｜JSConf EU 2019 (Offline-first data: Getting Bigger by Kevin Doran | JSConf EU 2019)
Uploaded: 2021-01-14T10:27:26.000Z
Duration: 24 min 58 s
Description: VoiceTubeの動画で発音を聞きながら英語表現を覚えよう！学べる英語：

法助動詞 A2

I'm really excited to be speaking at J s.

Uh, I've never really spoken at a conference before, or at least one with.

Um, it's really exciting, because in 2015 Patricia Garcia gave a talk here in Berlin A J S.

I wasn't there for it, but I saw it a year or two later on YouTube.

Um, and I kind of figured out where her Lincoln profile was.

So I found her get her profile, and I found a link to Repo, um, at Justin's organization, which is field intelligence, where I work now by email.

Two weeks later, I was on a plane to Nigeria, and now Patricia and I are colleagues, and I'm speaking here about, um, offline first stuff.

Um, So the work we do is in, um, trying to deliver health care commodities where it's a bit tougher to deliver them, expanding access with partnering federal governments and with down to small pharmacy traders.

Um, and doing that with software supply chain software um so we're headquartered in Abuja, where we work.

It's in the middle of the that just below the red part in Nigeria.

And, um, kind of one of the reasons why Nigeria is because it's huge and it's growing like crazy.

It has a massive market, and it's like about 1/6 of the continent, like 200 million people.

We're a small team of soft developers, operations people.

We have an office there, a small one here in Berlin and then a couple operations offices in Lagos and Nairobi.

Um, so three years ago, four years ago, when the company started, you kind of asked the question.

OK, what text stack are we gonna use for pharmacy supply chain management?

There's a lot of them you can customize on top of ah development platform, like an oracle or a s, a p lot of warehouses in places and Nigeria do this or you do what a lot of large companies do.

A lot of large tech companies and Fortune 500 companies where they, um, just build their own.

And if you're gonna do that and it's 2015 2016.

You're probably gonna choose, like a very boring but sensible stack, maybe something like C sharp dot net or jango with python or ruby on rails, something with a post press or some sort of sequel.

Um, which works really nice with enterprise resource planning.

You get a lot of stuff out of the box, a lot of tools that can really help you.

Um, but for us, our requirements were a lot different than that.

And the contrast that I kind of like to invent.

People will talk about these cities in different ways, but I like to think of Abuja and Lagos as the two places we need to operate and Legos.

For people who have been there is a mega city.

It has tons of growth, tons of money, tons of opportunities.

And then it also has, um, networks that sometimes work and sometimes don't work.

You connect thio the Internet on a cell tower.

But then there's a traffic jam right outside of your business, and suddenly 10,000 people are trying to use the same cell tower and you don't have network.

And then Abuja is a planned administrative city of just like a 1,000,000 people.

People don't carry cash they pay with bank cards.

Are partners at the federal government, have this giant command center room that has network.

That fall is because you talk and they need to see what's going on in the whole country.

Um, so we want to make something that's better than just a traditional, boring Web application.

We need something that can work in both of these places, Um, and so that means doing something that's offline, capable and offline is not binary.

It's not a it's an offline, capable operates or it's an online app.

You have Well, it looks crazy on the screen.

You have, like a lot of different options.

Um, the 1st 1 is what we called small offline.

These are names we made up for these categories, and it's kind of like a marketing gimmick that a lot of Web based APS use where they say we're offline, capable and people who aren't software developers don't know what that means, but like we know what this means.

It's like kind of like you're working on an issue ticket and get hub and you lose the network, an activity you can keep typing.

Maybe it's thrown into local storage, but you don't want to, like, refresh.

You don't want to click around so we couldn't use this model.

Um, medium offline, which is our word for like just using a native app like a iPhone app, an android app or writing for Platt like Windows or Mac, a less is a lot more attractive, and I've done work on acts like that before for pharmacy supply chain.

Our company has well, and it's not something that we're necessarily gonna rule out in the future, but it is still very manual.

There's question marks for how offline it is because it totally depends on you.

Is the developer what kind of data base that you're working with?

What rules are you setting up and how are you sinking with remote.

So like the example is like you pay tohave offline features in consumer APS like like Spotify and like do a lingo that give you offline features That duel Inglis seems to work really well.

But like Spotify eyes, it seems like every time I get on a plane, it forgets what I said to download off line.

Um, big offline is really important to think about, because this is how hospital I t systems work most of them.

But what you've had over the past couple of decades is Excuse me like a very large on site deployment of servers, even a server warehouse.

You have high tea staff, you have a local area network, and it's because clinicians need their software to work off line.

It's not like offline is new to tech companies in this industry, But as I said, like, that's not gonna work for us.

We can't put a server in, um, like, right now we're working with about 30,000 pharmacies, and there's hundreds of thousands to plan for.

So we went with the Web with offline first in the Web.

Lo I t support You could do the whole thing off line, but it's still the Internet.

Um, and there's a lot of talks on which distributed database to use, like the basic set up for an offline app.

Web app is, You put a service worker in you tell it to cash the static application, and then you work with local storage in the browser, which has become a lot more attractive over the last several years.

You get to use a lot of the user's available disk space, a percentage of it.

But how do you work with the in browser database?

And, um, Couch TB and pouch TV, which some people at this conference helps build, are kind of like the tools that most people end up using.

We're really happy with, um, the area that they cover for us.

If you know of some cool tool that somebody has, like this question that I often get is like, Oh, why don't you just write your own super cool like replicating thing that uses Blockchain and Kafka and is events sourced and the thing is that, like with these two are problem is never in the actual replication protocol.

We're never We don't have engineers sitting around wasting time trying to figure out what steps went wrong.

If there's a little bit of network, the documents sink.

So these two have been really useful for that.

Like somebody gave a talk a while ago where they said friends don't let friends build their own replication protocols.

字幕リスト動画再生

オフラインファーストのデータ。ケビン・ドーランの「大きくなるために」｜JSConf EU 2019 (Offline-first data: Getting Bigger by Kevin Doran | JSConf EU 2019)

stuff

access

current

capable