That all depends on the architecture that we're looking at, but at minimum you'll have a list of resources that the architecture makes use of; the basic building blocks of the system, like Notification Services, Queues, Functions and Event Buses, a set of "flows" that the architecture might encounter, which begin with events, like a customer logging in, completing an order, or adding products to their wishlist, and go on to explain how each subsequent step is implemented in the architecture, and finally, a security breakdown, including what is accessed internally/externally, and first party or third party connections to/from your systems.

This is like the Serverless Architecture Document above, but much more concise. It contains a less technical breakdown of core features, which is great for any stakeholders, third parties, or executives, who often want the cliff notes over the nitty gritty. That's not to say that it doesn't contain details - the Systems Brief is designed to outline everything in your architecture that matters from a top level.

At this point, no. I'm primarily consultation, though I have previously worked in teams that focused on implementation, mostly in AWS. If you're looking for me to integrate your existing systems or automate parts of your business, I do have other services available for that, which you can find on my profile.

Ideally, give it straight to a development team. Once the document is completed, it's designed to be used as both a scratchpad and a bible - the team should be using it to inform their design, take note of considerations, and if needed, make amendments or modifications based on your changing business needs.

When you order a document, after handover, that copy is yours - you or your team are free to modify it as you see fit. I keep the original copy of the document, and can make my own modifications.

Contact me! I'm available Fridays in the late afternoon and Saturdays/Sundays all day. I'm always happy to discuss further, and if it's within two weeks of handover, amendments can be made as we go.

Ideally, one or two a week, maximum. With meetings, as a long time engineer, I believe in quality over quantity. We won't be doing weekly catch-ups, but if you've got crucial information, a change request, new requirements or anything of the sort, feel free to reach out and we can book in more time. I'm always available through other avenues of communication as well, so feel free to email.

I've delivered three large-scale integrations, walking through design, architecture and handling the implementation itself in AWS. All three were in the finance sector, and involved handling of sensitive information as a part of the security considerations. For smaller projects, I've worked with hundreds of Australian businesses in both systems architecture consulting and delivery of business automation solutions, integrating platforms like Shopify, Hubspot, Pipedrive, Xero, SimPRO and more. As for myself, I've worked in this sector as a lead software engineer, and have been both a team lead and senior developer on large-scale integration projects, app builds and the like.

I do. Due to scale, there are some additional considerations that I would need to cover in our initial briefing, and from there we would make a decision based on your needs and my time constraints.