Tweet
Tweet

Slide 1

Slide 1 text

Warum IDEs
 sich verändern müssen Martin Lippert - Pivotal mlippert@pivotal.io @martinlippert

Slide 2

Slide 2 text

back in time…

Slide 3

Slide 3 text

Applications of that time

Slide 4

Slide 4 text

http://blog.ionelmc.ro/2015/02/24/the-problem-with-packaging-in-python/

Slide 5

Slide 5 text

No content

Slide 6

Slide 6 text

No content

Slide 7

Slide 7 text

No content

Slide 8

Slide 8 text

No content

Slide 9

Slide 9 text

Today?

Slide 10

Slide 10 text

Cloud-Native Apps

Slide 11

Slide 11 text

No content

Slide 12

Slide 12 text

How did applications change?

Slide 13

Slide 13 text

app/web server big monolith WAR the good old days UI Business Logic Data Access the database

Slide 14

Slide 14 text

app/web server big monolith WAR UI Business Logic Data Access the database need to scale?

Slide 15

Slide 15 text

app/web server big monolith WAR need to scale? UI Business Logic Data Access the database app/web server big monolith WAR UI Business Logic Data Access

Slide 16

Slide 16 text

EAI Bus communication? the database app/web server big monolith WAR UI Business Logic Data Access

Slide 17

Slide 17 text

single language apps

Slide 18

Slide 18 text

Today?

Slide 19

Slide 19 text

the world has changed… container JAR microservice container JAR microservice container JAR microservice container JAR microservice container JAR microservice container JAR microservice container JAR microservice container JAR microservice container JAR microservice JAR microse microservice container JAR microservice microservice container JAR microservice container JAR microservice JAR microservice container JAR microservice container JAR microservice container JAR microservice container JAR

Slide 20

Slide 20 text

How does that change application development?

Slide 21

Slide 21 text

many small service apps

Slide 22

Slide 22 text

many different languages and options

Slide 23

Slide 23 text

changing a running system

Slide 24

Slide 24 text

working on a few container JAR microservice container JAR microservice container JAR microservice container JAR microservice container JAR microservice container JAR microservice container JAR microservice container JAR microservice container JAR microservice JAR microse microservice container JAR microservice microservice container JAR microservice container JAR microservice JAR microservice container JAR microservice container JAR microservice container JAR microservice container JAR

Slide 25

Slide 25 text

too large to run everything locally on your machine

Slide 26

Slide 26 text

We need to change the way we work with microservices in IDEs

Slide 27

Slide 27 text

An example: The Spring Boot Dashboard

Slide 28

Slide 28 text

An example: Mixed scenarios

Slide 29

Slide 29 text

And from the inside?

Slide 30

Slide 30 text

IDEs are usually built as a fat client application, like 20 years ago

Slide 31

Slide 31 text

+ plug-ins

Slide 32

Slide 32 text

causing some UX inconsistencies…

Slide 33

Slide 33 text

No content

Slide 34

Slide 34 text

resource consumption is tremendous

Slide 35

Slide 35 text

plugin development is hard and a lot of work

Slide 36

Slide 36 text

Are cloud IDEs the solution?

Slide 37

Slide 37 text

pros and cons

Slide 38

Slide 38 text

but what else?

Slide 39

Slide 39 text

lightweight editors

Slide 40

Slide 40 text

language server protocol (welcome Visual Studio Code)

Slide 41

Slide 41 text

cloud-connected IDEs

Slide 42

Slide 42 text

Thanks Q&A Martin Lippert - Pivotal mlippert@pivotal.io @martinlippert download the Spring Tool Suite via: http://spring.io/tools