lambda - Best practices for storing data with Azure Functions -


i've been working lot microservices , common pattern every service responsible own data. service "a" can not access service "b" data directly without talking service "b" via http api or message queue.

now i've started pick work azure functions first time. i've looked @ fair few examples , seem have old function dabbling data in shared data store (which seems we're going old style of having massive monolithic database).

i wondering if there common pattern follow data storage when using function service? , responsibilities lie?

the following screen snippet example of event-driven distributed model of business processors in cloud-based solutions without using monolithic database. more details concept , technique can found in article using azure lease blob

businesscontextwithaf

note, each business context has own lease blob holding state of processing references other resources such metadata, config, data, results, etc. concept allows create matrix (multi) dimensional business processing model, each sub-nested process can have own lease blob.


Comments

Popular posts from this blog

Is there a better way to structure post methods in Class Based Views -

performance - Why is XCHG reg, reg a 3 micro-op instruction on modern Intel architectures? -

jquery - Responsive Navbar with Sub Navbar -