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

hanami minsk talk

hanami minsk talk

English transcription of my hanami Minsk talk

Anton Davydov

April 23, 2016
Tweet

More Decks by Anton Davydov

Other Decks in Programming

Transcript

  1. Hello Minsk!
 When I was preparing for my first conference

    all my friends scared me with various myths about Minsk
  2. I'm very nervous, cause it's my first presentation in English

    and if I make any mistakes I apologize in advance my name is Anton
  3. Also you can find my commits in other big projects

    like ruby, rails, crystal, etc.
  4. Besides I am trying to improve my local user group.

    That's why I am making drynkups in moscow.rb and I'm a curator of Collective twitter account for ruby developers.
  5. There is a nice word in Japanese which sounds as

    “hanami”. It means “watching the flowers bloom” The most popular flower is sakura but other flowers such as tulips are watched as well.
  6. As you might understand today we aren’t going to watch

    blooming sakura , although the weather is perfect outside.
 I’m going to talk about ruby web framefork which is called hanami.
  7. This framework was written by developer from Italy, his name

    is Luca. 
 The first commit was created three years ago. As you can see, hanami is a relatively new framework
  8. At this moment only few companies used this framefork in

    production. I found five companies and two of them - are Russian companies.
  9. the first idea is modularity It enables you to you

    to switch code and framework parts. Do you want to change model to AR or ROM? No problem, it’s easy. Do you think that there is too much of hanami ? You can use just routes.
  10. Simplicity. If you use simple tool you can start working

    on production application faster.
 I want to ask few questions: • Who read at least one book about sinatra or grape? • about rails? • And who read more than five books about rails? I think I read five different books about rails. Framework is just a tool, don't make a cult of it
  11. DSL is rather a controversial approach. And Martin Fowler has

    great posts about this. 
 We all love configuration DSL.
 But if you write DSL code using business logic, you have a big problem.
  12. few conventionals:
 If you are going to use hanami, you

    gain more freedom. You don't need to think how you can mix your application and framework conventional. You're like a Samurai who chooses his own path
  13. the most important part of my talk is in the

    next slide. Please, pay attention to it.

  14. hanami is not rails.
 hanami is not rails killer.
 And

    comparison of these frameworks is a stupid idea. But we'll compare them later
  15. business logic and data flow That's why it's normal to

    split this parts in your application. I'll start talking about a data flow
  16. Let's refresh in the memory what great people say. They

    recommend a monolith- first strategy. And hanami has a simple way to create monolith apps. This way is called Application Architecture. It looks like a typical rails application
  17. After that, your startup will make money and ,of course,

    you'll want to rewrite all you code to microservices.
 And hanami has a simple solution of this problem. It looks like this:
  18. You can see that now hanami app has an apps

    folder. In this folder you can find two different applications.

  19. In my example the first app is admin. This app

    contains all parts of monolithe app.
  20. I told that hanami is a modular web framefork. Let's

    look into its parts. The hanami organization has ten different gems
  21. • hanami - base part, this gem mixes all other

    gem together and provides CLI • router - Rack compatible HTTP router for Ruby • controller - Full featured and fast actions for Rack • utils - Ruby core extensions and class utilities • model - Persistence with entities and repositories
  22. the next five • validations - Validations mixin for Ruby

    objects • helpers - View helpers for Ruby applications • view - Presentation with a separation between views and templates • assets - Assets management for Ruby • mailer - Mail for Ruby applications
  23. I know that all of this looks frightening. That’s why

    let's look at differences with other frameforks
  24. In this part of my speech I'll show you only

    code samples, because one famous person Said:
  25. Hanami routes again. I lied to you. Because in this

    example I use block notation instead of class. it's logical to compare rails action and hanami action. And I have a really good example of rails action
  26. I told about it. hanami and rails are very different

    the only thing that unites them is MVC and ruby. That's why I'll cover all parts of MVS and show you how it is realized in rails and hanami.
  27. rails controller in DHH style.
 One controller is one class

    too. But this class can be included to only REST actions.
  28. Hanami. You can see that action is a class and

    controller module. Action has only one public method call.
 Yes, it looks a like service object.
  29. on this slide you can see a simple AR class.

    With validations, database logic, data logic and associations.
  30. of course, you can use the ROM. but I think

    rom has a big number of unnecessary parts and also you'll need to realize adaptors, command mappers, etc
  31. Hanami is a cross between rails and ROM. The model

    has two parts: entity and repository. In entity you work only with data
  32. in repository you work only with DB logic. For example

    if you want to create, delete or select record you need to use repository
  33. I have only one slide with string puralize method. You

    can see that rails monkeypatch core class and hanami create separate class
  34. How it works in rails
 we have a view folder

    with templates and instance variables which we call in our templates. Also we have helper modules. I think that everybody in this room knows that rails helpers have some problems.
 For example a few days ago I got a bug when one person initialized three methods with one name and after that he had problems.
  35. In hanami we have a view object. A view object

    is a typical ruby class where you can put all your? view logic and call this in templates.
 Also we have templates and also hanami has getters from controller instead instance variable. so and the last part
  36. assets Unfortunately I don't like this, that's why I'll leave

    it as an elective for independent review
  37. As you can see in let block I initialize new

    action
 this is a simple ruby instance.
  38. after that I can test it like a usual object

    no magic with get and post helpers. Only ruby objects 

  39. No monkey-patching
 I don't know about you but I really

    often have similar questions on SO.
 Why is it important? The general idea lies in erasing boundaries between language and framework.
  40. Best practices. I hope that great tool does not just

    work correctly this tool inculcates good practices for developer and product I think that hanami is a great tool because:
  41. This framework uses test first principles.
 As you can see,

    hanami applications have a good testing API.
 You’ve seen earlier how you can test controller, views and models are easily
 tested as well
  42. oh no, I'm so sorry, I forgot that tdd is

    dead Let's talk about cons
  43. TDD. this is not just a problem of hanami but

    sometimes you find yourself writing too many tests
 Also after some time you don't understand how and why you need to test some class
  44. I think you notice that this framework is verbose. -

    and if you write a simple admin with CRUD? Itstarts driving you mad
  45. The evident problem is the framework version instability. We occurred

    active changes in modelI remember those times when link_to helper didn’t work correctly. Gem was renamed thanks to IBM
  46. Hanami is very young comparing with rails which is 10

    years old and Sinatra is 8.That's why some useful gems are missing.And I think you can’t create a blog for 15 minutes because many parts you‘ll have to create manually
  47. if you are a mode boy and want to work

    with all of this I have some bad news for you. Hanami doesn’t support all of this.But if you want to try to use it, don't forget a developer’s manifesto
  48. yes, we all love benchmarks. And I know that benchmarks

    are only fanaticism, but everyone loves charts.
  49. for this I used puma with rackup files and wrk

    for stress test. you can find github link bellowif you have any ideas how I can improve my benchmarks I'll be happy to talk about this
  50. on the first chart I compare rack and hanami routes.

    I think that this result was predictable
  51. and the last chart shows rails and hanami. For this

    I created empty rails and hanami applications. After that I added two actions for each application. first action responde view, and second api. Draw your own conclusions.
  52. so, now I want to talk about my experienceI can

    group All my hanami applications in two and half parts
  53. There were either pure json api, or web applications with

    admin pages.Also I created public application which mixed api and web part.
  54. I liked doing apis and actions. Actions let you test

    your urls. Well, you have more coding but it brings you positive feelings. Now I can say that my next api will be on hamani. I really love controllers and models realisation
  55. And finally. Web apps with admin pages. I’ve told before

    , typical admin pages are a very bad part of hanami projects. You need to work with assets and with views and now it is still raw. But I hope that in the future it is going to be much better.
  56. Last point of my talk: gems I will answer honestly,

    there are few of them , but they are being written. Now I’m working with integrate with rodauth from Jeremy. Previously I worked with file upload gem
  57. if you are interested with hanami, see this links. On

    this slide you can find all necessary links: link to the main site chat and forum