{"id":4587,"date":"2018-05-21T22:46:35","date_gmt":"2018-05-21T21:46:35","guid":{"rendered":"https:\/\/blog.fabianpiau.com\/?p=4587"},"modified":"2022-01-05T15:08:11","modified_gmt":"2022-01-05T15:08:11","slug":"devoxx-uk-day-1","status":"publish","type":"post","link":"https:\/\/blog.fabianpiau.com\/en\/2018\/05\/21\/devoxx-uk-day-1\/","title":{"rendered":"Devoxx UK 2018 – Day 1"},"content":{"rendered":"

 <\/span>Version fran\u00e7aise disponible<\/strong><\/a><\/p>\n

This year I attended the 2 days of conference at Devoxx UK<\/a> taking place in London on 10-11th May. This article is a summary of the notes I took during the first day. If you’re interested in more details in a talk, you can watch the associated video.<\/p>\n

\"Devoxx<\/a>

Devoxx UK took place in the Business Design Centre in London<\/p><\/div>\n


<\/p>\n

A Future without Servers, with Danilo Poccia<\/h4>\n

How to build the best software with the best user experience?<\/strong><\/p>\n

Work backwards from the customer and before starting any implementation:<\/p>\n

    \n
  1. Write a Press Release<\/li>\n
  2. Write the FAQ<\/li>\n
  3. Define the Customer experience<\/li>\n
  4. Write the User manual<\/li>\n<\/ol>\n

    The idea is to get your system simple. A complex system was simple at the beginning, it became complex!<\/p>\n

    Architecture is changing:<\/strong><\/p>\n

      \n
    • 10 years ago: we are splitting our monolith applications using XML and SOAP for the communication<\/li>\n
    • 5 years ago: we are creating micro services architecture using REST\/JSON or binary protocol for the communication<\/li>\n
    • Now: we are building event-driven architecture with ephemeral functions<\/li>\n<\/ul>\n

      What about the data?<\/strong><\/p>\n

      Data repositories are becoming a source of events. Each event is an immutable information about business.<\/p>\n

      There is a shift from ACID (Atomic, Consistent, Isolated, Durable) to ACID 2.0 (Associative, Commutative, Idempotent, Distributed).<\/p>\n

      With event-driven design, we think cause \/ effect instead of triggers: “Service B is caused by A” instead of “Service A triggers B”. We use notification and acknowledgement mechanism.<\/p>\n

      So what does the future will look like?<\/strong><\/p>\n

      We will write only business logic code!<\/p>\n