BEGIN:VCALENDAR
PRODID:-//github.com/rianjs/ical.net//NONSGML ical.net 4.0//EN
VERSION:2.0
BEGIN:VTIMEZONE
TZID:America/Phoenix
X-LIC-LOCATION:America/Phoenix
END:VTIMEZONE
BEGIN:VEVENT
DESCRIPTION:Over the years there have been multitudes of issues with softw
 are design and development. These include the following:\n<ul>\n<li>Softw
 are can’t be tested well with automated test suites because part of the l
 ogic needing to be tested is dependent on oft-changing front end UI’s and
  API endpoints</li>\n<li>impossible to shift from a human-driven use of t
 he system to a batch-run system</li>\n<li>difficult or impossible to allo
 w the program to be driven by another program when that becomes attractiv
 e</li>\n</ul>\nUsing the Hexagonal Architecture or the Ports and Adapter 
 Pattern allows your APIs specifically to work better due to:\n<ul>\n<li>A
 llowing a clear decoupling of the API endpoints\, Data Access (Synthetic 
 or Production) and finally the Data Domain classes.</li>\n<li>The API End
 points (Controllers) have no knowledge or responsibility of Data Domain a
 nd behind it Data Access</li>\n<li>Because of the decoupling and separati
 on of responsibilities testing can be done easily and without issues.</li
 >\n<li>Data Access segments of the architecture can easily be switched ou
 t without impacting the Domain or API Endpoints</li>\n</ul>\nBy using the
  Hex Architecture not only does the development story become easier but y
 our end users get a much more stable API set to consume. The talk will ex
 plain and get you started on using these concepts with your ASP.NET Core 
 2.0 Web API projects.\n
DTEND;TZID=America/Phoenix:20171014T163000
DTSTAMP:20260416T183414Z
DTSTART;TZID=America/Phoenix:20171014T153000
GEO:33.293070;-111.796620
LOCATION:Chandler - Gilbert Community College - IRN-231
ORGANIZER:
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:Over the years there have been multitudes of issues with software 
 design and development. These include the following:\n<ul>\n<li>Software 
 can’t be tested well with automated test suites because part of the logic
  needing to be tested is dependent on oft-changing front end UI’s and API
  endpoints</li>\n<li>impossible to shift from a human-driven use of the s
 ystem to a batch-run system</li>\n<li>difficult or impossible to allow th
 e program to be driven by another program when that becomes attractive</l
 i>\n</ul>\nUsing the Hexagonal Architecture or the Ports and Adapter Patt
 ern allows your APIs specifically to work better due to:\n<ul>\n<li>Allow
 ing a clear decoupling of the API endpoints\, Data Access (Synthetic or P
 roduction) and finally the Data Domain classes.</li>\n<li>The API Endpoin
 ts (Controllers) have no knowledge or responsibility of Data Domain and b
 ehind it Data Access</li>\n<li>Because of the decoupling and separation o
 f responsibilities testing can be done easily and without issues.</li>\n<
 li>Data Access segments of the architecture can easily be switched out wi
 thout impacting the Domain or API Endpoints</li>\n</ul>\nBy using the Hex
  Architecture not only does the development story become easier but your 
 end users get a much more stable API set to consume. The talk will explai
 n and get you started on using these concepts with your ASP.NET Core 2.0 
 Web API projects.\n
UID:6fc7e036-ad57-4c7d-bcc8-6e2942fc0dfe
END:VEVENT
END:VCALENDAR