Event-Driven Architecture 101 working sessions

An event-driven architecture uses events to trigger and communicate between decoupled services and is common in modern applications built with microservices. An event is a change in state, or an update, like an item being placed in a shopping cart on an e-commerce website. Events can either carry the state (the item purchased, its price, and a delivery address) or events can be identifiers (a notification that an order was shipped).

TrackIt consultants will conduct a design sprint in conjunction with your team to produce a conceptual architecture and MVP user interface overview for your product.

Discovery

The software development effort to produce a Minimum Viable Product (MVP) would be a follow-on phase, enabled by this design effort. Scoping of the MVP development should be able to be validated following the delivery of the design deliverables outlined below.

• Four, or if necessary more, 2-3 hour sessions will be planned over the course of approximately two weeks with TrackIt members and your team stakeholders.
• One TrackIt user interface developer and one TrackIt back-end software developer at the minimum will participate in the joint sessions.

Upon completion of the design sprint TrackIt, with your input during and after the joint sessions, will provide (not an exhaustive list):

1. Architecture Diagrams
2. API Workflow
3. AWS Infrastructure
4. WebFlow Diagram
5. Wireframes
6. Content Owner page
7. MVP User Stories With Effort Level

Documentation and knowledge transfer