We are used to quickly start drawing a solution in-session. Our latest pre-sales appointment was no exception to this. With time, these early drawings have even become
Read moreAPI design and abstraction
Explaining an API key features (natural design for REST routes, extendability brought by high level of abstraction, …) by sharing them on a whiteboard says much
Read moreOutline and explain
Way before we get deep into the implementation details, we always make sure everyone adheres to the goals and how the system should work with
Read moreBirth of a solution
A whiteboard and a crowd is generally pretty much what’s required to imagine a new solution altogether. This one is the very first drawing of a
Read moreStreams of data
Good use cases helps capturing the streams of data and will guide to a properly designed solution. This is one out of the many we have
Read moreSizing a platform
When designing a solution, we like to go through all the design aspects. Take some time and decide on the proper deployment plan and platform
Read moreDesign for performance
Designing a solution without thinking about how it is actually going to be used now and then is rather risky. We treat future performance and system
Read moreDesign a solution’s components
Designing the BOM’s abstraction model for multi providers support. Smart implementations often start with a chat around a whiteboard refining a model.
Read moreCapture requirements
Key points of a solution are always to be searched in the requirements. Gathering them all helps drawing the proper design, whatever their type.
Read more