BEGIN:VCALENDAR
VERSION:2.0
PRODID:icalendar-ruby
CALSCALE:GREGORIAN
BEGIN:VTIMEZONE
TZID:Europe/London
BEGIN:DAYLIGHT
DTSTART:20220327T020000
TZOFFSETFROM:+0000
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:BST
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20221030T010000
TZOFFSETFROM:+0100
TZOFFSETTO:+0000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:GMT
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:20260619T091851Z
UID:XEEGEQ
DTSTART;VALUE=DATE:20220616
DTEND;VALUE=DATE:20220617
CLASS:PUBLIC
CREATED:20220506T110538
DESCRIPTION: NE Bytes June 16 2022 \n\n 18:30 - 21:00 BST \n\n This month w
 e have two awesome talks for you.  \n\n Meeting Link \n\n We are using Mic
 rosoft Teams for this event. Click on the link and join in your browser or
  download the app if you prefer. \n\n https://teams.microsoft.com/l/meetup
 -join/19:meeting_ZjA0Yjg1NjUtZGYwZC00YTEyLWFlYzgtZjliZjY2MzlmMzZk@thread.v
 2/0?context={"Tid":"10a6d4fc-3a63-42d9-8a1e-744f8d79928d"\,"Oid":"d7c0b386
 -3919-46a1-907a-cd184ea3958b"} \n\n \n\n More Testable Code with the Hexag
 onal Architecture \n\n Hexagonal Architecture provides a set of simple and
  specific rules to organize your system's code. These rules make it easier
  to test your code\, as well as being a good fit for incorporating Domain-
 Driven Design. In this talk\, we'll look at how Hexagonal Architecture dif
 fers from typical architectures. We'll then dive into how Hexagonal Archit
 ecture leverages the idea of Separation of Concerns to make testing easier
 . We'll see how the architecture uses Ports &amp\; Adapters (another name 
 for this architecture) to improve the design by clearly defining how exter
 nal resources connect to the core of our application's logic. \n\n \n\n Te
 d M. Young \n\n Ted M. Young (known as JitterTed on social media) is a Jav
 a trainer\, coding coach\, speaker\, and author. He's been in software dev
 elopment for over 30 years\, doing eXtreme Programming since 2000. Ted has
  worked for eBay\, Google\, Apple\, and Guidewire Software. He is now an i
 ndependent educator\, helping those new to the industry and experienced fo
 lks increase their joy in coding by making code more testable. Ted's favor
 ite techniques are test-driven development\, refactoring\, domain-driven d
 esign\, and Hexagonal Architecture. \n\n \n https://twitter.com/jitterted 
 \n https://www.subscribepage.com/maketestable \n \n\n \n\n Event Sourcing 
 and CQRS on Azure Functions \n\n In this talk I outline a system built usi
 ng Azure serverless functions and event grid\, the CQRS architecture and w
 ith the underlying entity storage being by event sourcing. The prototype s
 hows how this allows you to assemble a highly performant\, geographically 
 distributed system which scales up and down rapidly for an extremely small
  cost. \n\n CQRS is an application design pattern (or architecture) that d
 iffers from single model architectures (like MVC or MVVM) in that the part
 s of the system responsible for changing the state of the system (the Comm
 and side) is entirely separate to the parts of the system responsible for 
 getting the state of the system (the Query side). \n\n Event Sourcing is a
  data architecture that flips the way we store data on its head. Instead o
 f storing the state of any given object as it currently is and updating th
 at state\, we instead store the complete history of every change that has 
 occurred to the object and allow us to derive the state of the object by r
 unning code known as a projection over that event history. \n\n Azure Even
 t Grid is a set of connected technologies provided by Microsoft as part of
  their Azure cloud which are designed to facilitate an event-driven archit
 ecture. It consists of event triggers that can be set up to either fire on
  a state change event and these triggers are linked by the Event Grid to r
 oute the events from their trigger to a destination - and azure serverless
  function. \n\n Merrion-Duncan Jones \n\n A .NET developer with a backgrou
 nd in the financial services industry. He has a personal interest in highl
 y scalable systems\, which has lead to Event Sourcing (by way of CQRS)\, a
 nd has developed a Visual Studio plug-in to for creating CQRS and Event So
 urcing based systems via a visual interface. \n\n \n https://twitter.com/M
 errion \n \n
LAST-MODIFIED:20220811T095903
LOCATION:Microsoft Teams Meeting
ORGANIZER:mailto:noreply-calendar@tito.io
SUMMARY:June 16 2022 NE Bytes - More Testable Code with the Hexagonal Archi
 tecture + Event Sourcing and CQRS on Azure Functions
URL;VALUE=URI:https://ti.to/ne-bytes/june-2022-hexagons-and-event-sources
URL;VALUE=URI:https://ti.to/ne-bytes/june-2022-hexagons-and-event-sources
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260619T091851Z
UID:XEEGEQ1046270
DTSTART;TZID=Europe/London:20220616T183000
DTEND;TZID=Europe/London:20220616T210000
CLASS:PUBLIC
CREATED:20220506T110541
DESCRIPTION:## NE Bytes June 16 2022\n### 18:30 - 21:00 BST\n\nJoin us for 
 our next event of 2022 with two awesome talks and two awesome speakers. Ch
 eck the event website closer to the time for the Teams link.\n\n## More Te
 stable Code with the Hexagonal Architecture\n\nHexagonal Architecture prov
 ides a set of simple and specific rules to organize your system's code. Th
 ese rules make it easier to test your code\, as well as being a good fit f
 or incorporating Domain-Driven Design. In this talk\, we'll look at how He
 xagonal Architecture differs from typical architectures. We'll then dive i
 nto how Hexagonal Architecture leverages the idea of Separation of Concern
 s to make testing easier. We'll see how the architecture uses Ports & Adap
 ters (another name for this architecture) to improve the design by clearly
  defining how external resources connect to the core of our application's 
 logic.\n\n## Event Sourcing and CQRS on Azure Functions \n\nIn this talk I
  outline a system built using Azure serverless functions and event grid\, 
 the CQRS architecture and with the underlying entity storage being by even
 t sourcing. The prototype shows how this allows you to assemble a highly p
 erformant\, geographically distributed system which scales up and down rap
 idly for an extremely small cost.\n\nCQRS is an application design pattern
  (or architecture) that differs from single model architectures (like MVC 
 or MVVM) in that the parts of the system responsible for changing the stat
 e of the system (the Command side) is entirely separate to the parts of th
 e system responsible for getting the state of the system (the Query side).
 \n\nEvent Sourcing is a data architecture that flips the way we store data
  on its head. Instead of storing the state of any given object as it curre
 ntly is and updating that state\, we instead store the complete history of
  every change that has occurred to the object and allow us to derive the s
 tate of the object by running code known as a projection over that event h
 istory.\n\nAzure Event Grid is a set of connected technologies provided by
  Microsoft as part of their Azure cloud which are designed to facilitate a
 n event-driven architecture. It consists of event triggers that can be set
  up to either fire on a state change event and these triggers are linked b
 y the Event Grid to route the events from their trigger to a destination -
  and azure serverless function.\n\n### Merrion-Duncan Jones\n\nA .NET deve
 loper with a background in the financial services industry. He has a perso
 nal interest in highly scalable systems\, which has lead to Event Sourcing
  (by way of CQRS)\, and has developed a Visual Studio plug-in to for creat
 ing CQRS and Event Sourcing based systems via a visual interface.\n\nhttps
 ://twitter.com/Merrion\n
LAST-MODIFIED:20220531T190317
ORGANIZER:mailto:noreply-calendar@tito.io
SUMMARY:[June 16 2022 NE Bytes - More Testable Code with the Hexagonal Arch
 itecture + Event Sourcing and CQRS on Azure Functions] NE Bytes June 16 20
 22 - "More Testable Code with the Hexagonal Architecture" and "Event Sourc
 ing and CQRS on Azure Functions"
URL;VALUE=URI:https://ti.to/ne-bytes/june-2022-hexagons-and-event-sources
X-ALT-DESC;FMTTYPE=text/html:## NE Bytes June 16 2022\n### 18:30 - 21:00 BS
 T\n\nJoin us for our next event of 2022 with two awesome talks and two awe
 some speakers. Check the event website closer to the time for the Teams li
 nk.\n\n## More Testable Code with the Hexagonal Architecture\n\nHexagonal 
 Architecture provides a set of simple and specific rules to organize your 
 system's code. These rules make it easier to test your code\, as well as b
 eing a good fit for incorporating Domain-Driven Design. In this talk\, we'
 ll look at how Hexagonal Architecture differs from typical architectures. 
 We'll then dive into how Hexagonal Architecture leverages the idea of Sepa
 ration of Concerns to make testing easier. We'll see how the architecture 
 uses Ports & Adapters (another name for this architecture) to improve the 
 design by clearly defining how external resources connect to the core of o
 ur application's logic.\n\n## Event Sourcing and CQRS on Azure Functions \
 n\nIn this talk I outline a system built using Azure serverless functions 
 and event grid\, the CQRS architecture and with the underlying entity stor
 age being by event sourcing. The prototype shows how this allows you to as
 semble a highly performant\, geographically distributed system which scale
 s up and down rapidly for an extremely small cost.\n\nCQRS is an applicati
 on design pattern (or architecture) that differs from single model archite
 ctures (like MVC or MVVM) in that the parts of the system responsible for 
 changing the state of the system (the Command side) is entirely separate t
 o the parts of the system responsible for getting the state of the system 
 (the Query side).\n\nEvent Sourcing is a data architecture that flips the 
 way we store data on its head. Instead of storing the state of any given o
 bject as it currently is and updating that state\, we instead store the co
 mplete history of every change that has occurred to the object and allow u
 s to derive the state of the object by running code known as a projection 
 over that event history.\n\nAzure Event Grid is a set of connected technol
 ogies provided by Microsoft as part of their Azure cloud which are designe
 d to facilitate an event-driven architecture. It consists of event trigger
 s that can be set up to either fire on a state change event and these trig
 gers are linked by the Event Grid to route the events from their trigger t
 o a destination - and azure serverless function.\n\n### Merrion-Duncan Jon
 es\n\nA .NET developer with a background in the financial services industr
 y. He has a personal interest in highly scalable systems\, which has lead 
 to Event Sourcing (by way of CQRS)\, and has developed a Visual Studio plu
 g-in to for creating CQRS and Event Sourcing based systems via a visual in
 terface.\n\nhttps://twitter.com/Merrion\n
URL;VALUE=URI:https://ti.to/ne-bytes/june-2022-hexagons-and-event-sources
END:VEVENT
END:VCALENDAR
