Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Evolutionary architecture: evolving even the language

Evolutionary architecture: evolving even the language

Over the years the architecture of microservices has been widely adopted, since it provides numerous advantages such as: technological heterogeneity, scalability, decoupling and so on.

In this sense the microservices architecture meets the definitions of an evolutionary architecture, that is, an architecture designed for incremental changes even changes of languages.

In this lecture I will discuss the characteristics of Kotlin, motivations for its adoption in microservices rather than already consolidated languages ​​and lessons learned during its adoption and migration.

Ef3b48913ea26665c25b2ad78e449d16?s=128

Luram Archanjo

July 19, 2019
Tweet

Transcript

  1. Evolutionary Architecture: Evolving even the language Luram Archanjo

  2. Who am I? • Software Engineer at Sensedia • MBA

    in Java projects • Java and Microservice enthusiastic
  3. Agenda • Use case • Microservices • Evolutionary Architecture •

    Challenges to adopt Kotlin • Kotlin benefits • Questions
  4. Use case

  5. Use case Token Service Provider Tokenization reduces the value of

    stored payment credentials by removing consumers’ primary account numbers (PANs) from the transaction process. It does this by replacing them with a unique identifier called a payment token. This reduces the appeal of stealing the credentials as they would be largely useless to hackers. Source: https://www.rambus.com/blogs/what-is-a-token-service-provider/
  6. Use case

  7. Microservices

  8. Moving to Microservices Feature A Feature B Feature C Monolith

    Microservice Microservice Microservices Microservice
  9. Technological Heterogeneity Microservice Microservice Microservice DB DB DB

  10. Evolutionary Architecture

  11. Evolutionary Architecture An evolutionary architecture supports guided, incremental change as

    a first principle across multiple dimensions. Source: https://www.thoughtworks.com/books/building-evolutionary-architectures
  12. Our stack

  13. Evolutionary Architecture Languages Technologies Databases

  14. All(15) microservices were written in

  15. We wanted to change, but there were many challenges!

  16. • Expertise in Java Frameworks e.g: Spring Stack, Hibernate etc.

    • Expertise in Object-Oriented Programming • Learning curve, sprint in progress Evolutionary Architecture
  17. is going to overcome all of those challenges?

  18. Yes!!!

  19. Expertise in Java Frameworks Expertise in Object-Oriented Programming Learning curve,

    sprint in progress
  20. Expertise in Java Frameworks Interoperability: Kotlin is fully compatible with

    all Java-based frameworks, which lets you stay on your familiar technology stack while reaping the benefits of a more modern language. Java code Kotlin code Java Virtual Machine (JVM) Bytecode Source: https://kotlinlang.org/docs/reference/server-overview.html
  21. Expertise in Java Frameworks

  22. Expertise in Java Frameworks Expertise in Object-Oriented Programming Learning curve,

    sprint in progress
  23. Expertise in Object-Oriented Programming Object-oriented programming (OOP) is a programming

    paradigm based on the concept of "objects", which can contain data, in the form of fields (often known as attributes), and code, in the form of procedures (often known as methods). Source: https://en.wikipedia.org/wiki/Object-oriented_programming Code data class Person(val firstName: String, val surname: String, val age: Int) { fun fullName() = "$firstName $surname" }
  24. Expertise in Object-Oriented Programming Functional programming is a programming paradigm

    based structures and elements of computer programs, that treats computation as the evaluation of mathematical functions and avoids changing-state and mutable data. Source: https://en.wikipedia.org/wiki/Functional_programming Code data class Person(val name: String, String, val age: Int) val persons = listOf(Person("Person 1", 15), Person("Person 2", 22)) persons.filter { person -> person.age >= 18 }
  25. Expertise in Java Frameworks Expertise in Object-Oriented Programming Learning curve,

    sprint in progress
  26. Learning curve, sprint in progress Source: https://kotlinlang.org/docs/reference/server-overview.html Migration: Kotlin supports

    gradual, step by step migration of large codebases from Java to Kotlin. You can start writing new code in Kotlin while keeping older parts of your system in Java. Microservice Java Microservice Java Kotlin Microservice Kotlin
  27. Learning curve, sprint in progress

  28. Kotlin benefits

  29. 40% less code

  30. 40% less code Java public class Person { private final

    String name; private final Integer age; public Person(String name, Integer age) { this.name = name; this.age = age; } public String getName() { return name; } public Integer getAge() { return age; } } Kotlin data class Person(val name: String, val age: Int) Default Values data class Person(val name: String = "Unknown", val age: Int = 0) Initialization val person = Person("Luram Archanjo", 25) val person = Person() // Name = Unknown & age = 0
  31. Null Safety

  32. Null Safety Java final Person person = null; // accept

    null person.getName().length(); Exception java.lang.NullPointerException Kotlin val person: Person = null // compilation error val person: Person? = null // accept null person.name.length // compilation error Safe Calls person?.name?.length // return null Elvis Operator person?.name?.length ?: 0 // return 0 if null
  33. Performs lots of checks, reducing runtime errors and the number

    of bugs in the code
  34. Who is using Kotlin? Why?

  35. Who is using Kotlin? Why? Source: https://github.com/ygaller/kotlin-companies/wiki

  36. Fail-fast principle = Time to market

  37. Summary 2º Place 1º Place 3º Place Interoperable with Java

    • Known frameworks • Low learn curve Concise • Easier to maintain • Easier to read • Easier to apply changes when necessary Modern • Safe compiler • Type interface • Collection • Lambdas
  38. Thanks a million! Questions? /larchanjo /luram-archanjo