In general, I observed a few programmers that are keenly aware of their skill set, and tend to complain loudly about systems that hold people accountable by colocating their bad workmanship with their area of responsibility.
The secret of bolting on a good AMQP pattern is embedding signatures, GUID, UTC time, and expected state pre-conditions. The notion a problem domain even fits into a monolithic structure is laughably naive.
Usually, toy naive designs devolve into a dynamic object storage model on SQL, and it is ridiculously silly in this age.
The secret of bolting on a good AMQP pattern is embedding signatures, GUID, UTC time, and expected state pre-conditions. The notion a problem domain even fits into a monolithic structure is laughably naive.
Usually, toy naive designs devolve into a dynamic object storage model on SQL, and it is ridiculously silly in this age.
Best regards =3