pith. sign in

arxiv: 2504.19757 · v2 · submitted 2025-04-28 · 💻 cs.DB · cs.SE

vMODB: Unifying Event and Data Management for Distributed Asynchronous Applications

Rodrigo Laigner , Yongluan Zhou This is my paper

Pith reviewed 2026-05-22 18:40 UTC · model grok-4.3

classification 💻 cs.DB cs.SE
keywords event-driven microservicesACID propertiesdistributed systemsprogramming modelsdata consistencycloud applicationsvirtual micro serviceevent logs
0
0 comments X

The pith

vMODB unifies event logs and state management to enforce ACID properties across microservice components.

A machine-rendered reading of the paper's core claim, the machinery that carries it, and where it could break.

Event-driven microservice architectures force developers into a trade-off because separate database and messaging systems lack visibility into each other's state and transactions. vMODB introduces the Virtual Micro Service programming model that uses familiar ORM and meta-programming constructs to declare data models, constraints, concurrency rules, and component dependencies. This makes application semantics visible to the underlying system. The system then transparently unifies event logs and state management to deliver full ACID guarantees without requiring manual coordination code. Benchmarks on two workloads show the resulting system can run up to three times faster than a leading eventual-consistency framework.

Core claim

vMODB is a distributed framework whose core contribution is the co-design of the Virtual Micro Service programming model and a specialized execution system. The VMS model supplies Object-Relational Mapping and meta-programming constructs that let developers specify data models, constraints, concurrency, and dependencies. These declarations make application semantics visible, allowing vMODB to unify event logs and state management transparently and thereby enforce ACID properties across distributed asynchronous components while relieving developers of cross-component consistency responsibilities.

What carries the argument

The Virtual Micro Service (VMS) programming model, which uses ORM and meta-programming constructs to expose application semantics so the system can automatically unify event logs with state management for ACID enforcement.

If this is right

  • Developers can retain the scalability of event-driven designs while obtaining strong consistency and integrity across components.
  • Cross-component transactions become ACID-compliant without explicit distributed coordination logic.
  • Full-stack optimizations enabled by the co-design produce measurable performance gains over systems limited to eventual consistency.

Where Pith is reading between the lines

These are editorial extensions of the paper, not claims the author makes directly.

  • The visibility approach could reduce a common class of production bugs that arise from manually stitched consistency logic in microservices.
  • Similar semantic-exposure techniques might be adapted to other asynchronous settings such as serverless workflows or stream-processing pipelines.

Load-bearing premise

Exposing application semantics through the Virtual Micro Service model and meta-programming constructs is sufficient for the system to enforce full ACID properties across components without unacceptable overhead or violating asynchrony.

What would settle it

A cross-component transaction executed through vMODB that produces inconsistent state, violates isolation, or shows performance no better than manual coordination under realistic workloads.

Figures

Figures reproduced from arXiv: 2504.19757 by Rodrigo Laigner, Yongluan Zhou.

Figure 1
Figure 1. Figure 1: Architectural Overview of vMODB Coordinator. The coordinator plays a central role in the system, processing transaction requests from clients, computing the depen￾dencies of each VMS in a multi-VMS transaction, assigning mono￾tonically increasing TiDs and dispatching transaction requests with an assigned TiD to input VMSes, and coordinating the commit protocol. The coordinator is also an OS process; thus, … view at source ↗
Figure 2
Figure 2. Figure 2: VMS Internals 5.1.1 I/O Processing. Network communication with the coordina￾tor and among VMSes is achieved with TCP connections through asynchronous I/O [51]. This applies to both event logs and protocol messages. I/O threads are divided into two categories, receivers and senders. The OS kernel signals receivers about new network I/O events, which in turn unmarshal log entries from the buffers, deserializ… view at source ↗
Figure 3
Figure 3. Figure 3: Coordinator Internals The coordinator bootstraps with a handshake protocol. Users must specify a set of transactions (Listing 3) and corresponding "starter" VMSes, including their network addresses. At startup, the coordinator sends a presentation message to all VMSes and requests their VMS metadata, which includes their input and output event logs. With this information, the coordinator builds a consumer … view at source ↗
Figure 4
Figure 4. Figure 4: Throughput of TiD Assignment 6.1.3 Methodology. All experiments are run in 6 epochs of 10 seconds each, with the first 2 epochs used for warming up the systems. After each epoch, the components’ states and event logs are cleaned. To remove cache effects across experiments, we restart OM’s components after each experiment. We collect two metrics in the experiments: throughput and end￾to-end latency. End-to-… view at source ↗
Figure 6
Figure 6. Figure 6: Scalability (left) and Breakdown Latency (right) [PITH_FULL_IMAGE:figures/full_fig_p011_6.png] view at source ↗
Figure 9
Figure 9. Figure 9: Effect of Batch Size on Throughput 1 10 100 1K 10K 0 2,000 4,000 6,000 Num Txns/Batch w/o Seller Dashboard End-to-end Latency (ms) p50 avg p75 p90 1 10 100 1K 10K 0 5 10 Num Txns/Batch only Seller Dashboard [PITH_FULL_IMAGE:figures/full_fig_p012_9.png] view at source ↗
read the original abstract

Event-driven microservice architecture (EDMA) has emerged as a crucial architectural pattern for scalable cloud applications. In typical EDMAs, database systems are relegated to isolated storage engines for individual components, blind to cross-component transactions, while messaging systems are unaware of each component's application state. Consequently, EDMAs impose a severe trade-off: developers must either sacrifice strong data consistency and integrity or manually manage complex distributed coordination. To address this challenge, we design vMODB, a distributed framework that offers a better trade-off and enables developers to build highly consistent and scalable cloud applications without compromising the benefits of EDMA. The core contribution of vMODB lies in the co-design of a programming abstraction and the underlying specialized system. We propose Virtual Micro Service (VMS), a novel programming model that provides familiar Object-Relational Mapping (ORM) and meta-programming constructs for specifying the data model, constraints, concurrency, and dependencies, making application semantics visible to the system. vMODB leverages semantic visibility to enforce ACID properties by transparently unifying event logs and state management, relieving developers from the burden of ensuring cross-component data consistency and integrity. Thanks to full-stack system optimizations enabled by our co-design, experiments using two benchmarks show that vMODB outperforms a widely adopted state-of-the-art competing framework that only offers eventual consistency by up to 3x.

Editorial analysis

A structured set of objections, weighed in public.

Desk editor's note, referee report, simulated authors' rebuttal, and a circularity audit. Tearing a paper down is the easy half of reading it; the pith above is the substance, this is the friction.

Referee Report

2 major / 2 minor

Summary. The manuscript presents vMODB, a distributed framework for event-driven microservice architectures (EDMA) that co-designs a Virtual Micro Service (VMS) programming model with a specialized runtime. VMS uses ORM and meta-programming constructs to expose data models, constraints, concurrency, and dependencies, enabling the system to transparently unify event logs with state management and enforce ACID properties across components. This relieves developers from manual distributed coordination while preserving EDMA scalability. Experiments on two benchmarks report up to 3x performance improvement over a state-of-the-art eventual-consistency framework.

Significance. If the unification mechanism and performance results hold under scrutiny, the work could meaningfully advance practical development of consistent cloud applications by bridging messaging and storage concerns in asynchronous settings. The explicit co-design of abstraction and system, together with the falsifiable 3x speedup prediction against an eventual-consistency baseline, constitutes a concrete contribution that could be directly tested by follow-on implementations.

major comments (2)
  1. Abstract: The central claim that semantic visibility enables automatic enforcement of full ACID properties across components is stated at a high level but is not accompanied by any description of the underlying transaction protocol, isolation mechanism, or correctness argument. This absence is load-bearing for the primary contribution and prevents assessment of whether the approach preserves asynchrony or introduces hidden synchronization costs.
  2. Evaluation section (benchmarks): The reported 'up to 3x' speedup is presented without error bars, number of runs, variance statistics, or precise configuration details of the competing eventual-consistency framework. Without these, the performance claim cannot be verified and risks overstating the benefit of the unification.
minor comments (2)
  1. The introduction of 'Virtual Micro Service (VMS)' would benefit from an explicit comparison table against existing microservice and actor models to clarify novelty.
  2. Notation for 'semantic visibility' is used repeatedly but never given a concise formal definition or pseudocode example in the early sections.

Simulated Author's Rebuttal

2 responses · 0 unresolved

We thank the referee for the constructive comments and the recommendation for major revision. We address each major comment below with specific responses and proposed changes to the manuscript.

read point-by-point responses

  1. Referee: Abstract: The central claim that semantic visibility enables automatic enforcement of full ACID properties across components is stated at a high level but is not accompanied by any description of the underlying transaction protocol, isolation mechanism, or correctness argument. This absence is load-bearing for the primary contribution and prevents assessment of whether the approach preserves asynchrony or introduces hidden synchronization costs.

    Authors: We agree that the abstract presents the core claim at a high level without detailing the mechanisms. The manuscript body (Sections 3 and 4) describes the transaction protocol as a custom optimistic concurrency control scheme that unifies event logs with state updates, using semantic visibility to infer isolation levels without global locks. A correctness sketch appears in Section 5, arguing that asynchrony is preserved via deferred validation and local commit decisions. To make this accessible from the abstract, we will add one sentence referencing the protocol and its asynchrony-preserving properties. This is a targeted revision that does not expand the abstract length substantially. revision: yes

  2. Referee: Evaluation section (benchmarks): The reported 'up to 3x' speedup is presented without error bars, number of runs, variance statistics, or precise configuration details of the competing eventual-consistency framework. Without these, the performance claim cannot be verified and risks overstating the benefit of the unification.

    Authors: We accept this criticism. The current evaluation omits these details, which limits reproducibility. In the revised version we will (1) add error bars representing standard deviation to all graphs, (2) state that each data point is the mean of 10 independent runs, (3) report variance statistics explicitly in a new table, and (4) provide the exact version, configuration parameters, and deployment settings of the competing eventual-consistency framework. These additions will be placed in the evaluation section and its caption. revision: yes

Circularity Check

0 steps flagged

No significant circularity detected

full rationale

The paper presents an architectural co-design of the Virtual Micro Service (VMS) programming model and the vMODB runtime to make application semantics visible, thereby unifying event logs with state management for ACID enforcement. No equations, fitted parameters, predictions, or self-citations appear in the provided text that reduce any central claim to its own inputs by construction. The unification argument is justified directly by the proposed visibility mechanism rather than by renaming or fitting prior results. Empirical performance comparisons to eventual-consistency baselines are external and falsifiable, leaving the derivation chain self-contained.

Axiom & Free-Parameter Ledger

0 free parameters · 0 axioms · 2 invented entities

Review is based on abstract only; no free parameters, axioms, or invented entities beyond the high-level concepts of VMS and vMODB are described.

invented entities (2)
  • Virtual Micro Service (VMS) no independent evidence
    purpose: Programming model that exposes data model, constraints, concurrency, and dependencies to the system
    Introduced as the core abstraction enabling semantic visibility.
  • vMODB no independent evidence
    purpose: Distributed framework that unifies event logs and state management
    Central system proposed to enforce ACID properties transparently.

pith-pipeline@v0.9.0 · 5770 in / 1136 out tokens · 62317 ms · 2026-05-22T18:40:11.814626+00:00 · methodology

discussion (0)

Sign in with ORCID, Apple, or X to comment. Anyone can read and Pith papers without signing in.

Lean theorems connected to this paper

Citations machine-checked in the Pith Canon. Every link opens the source theorem in the public Lean library.

What do these tags mean?
matches
The paper's claim is directly supported by a theorem in the formal canon.
supports
The theorem supports part of the paper's argument, but the paper may add assumptions or extra steps.
extends
The paper goes beyond the formal theorem; the theorem is a base layer rather than the whole result.
uses
The paper appears to rely on the theorem as machinery.
contradicts
The paper's claim conflicts with a theorem or certificate in the canon.
unclear
Pith found a possible connection, but the passage is too broad, indirect, or ambiguous to say the theorem truly supports the claim.

Reference graph

Works this paper leans on

81 extracted references · 81 canonical work pages

  1. [1]

    DuckDB Foundation 2025. DuckDB. DuckDB Foundation. Retrieved March 4, 2025 from http://duckdb.org/

    work page 2025

  2. [2]

    Gul Agha. 1986. Actors: A Model of Concurrent Computation in Distributed Systems. The MIT Press. https://doi.org/10.7551/mitpress/1086.001.0001

    work page doi:10.7551/mitpress/1086.001.0001 1986

  3. [3]

    Andreas Andreakis, Falguni Jhaveri, Ioannis Papapanagiotou, Mark Cho, Poorna Reddy, and Tongliang Liu. 2019. Delta: A Data Synchronization and Enrichment Platform. Netflix. Retrieved April 8, 2024 from https://netflixtechblog.com/delta- a-data-synchronization-and-enrichment-platform-e82c36a79aee

    work page 2019

  4. [4]

    AWS. 2024. Amazon EC2 C5 Instances. Retrieved October, 16 2024 from https: //aws.amazon.com/ec2/instance-types/c5/

    work page 2024

  5. [5]

    AWS. 2025. What is EDA (Event-Driven Architecture)? Retrieved October, 16 2024 from https://aws.amazon.com/what-is/eda/

    work page 2025

  6. [6]

    Franklin, Ali Ghodsi, Joseph M

    Peter Bailis, Alan Fekete, Michael J. Franklin, Ali Ghodsi, Joseph M. Hellerstein, and Ion Stoica. 2015. Feral Concurrency Control: An Empirical Investigation of Modern Application Integrity. In Proceedings of the 2015 ACM SIGMOD Interna- tional Conference on Management of Data (Melbourne, Victoria, Australia) (SIG- MOD ’15). Association for Computing Mac...

    work page doi:10.1145/2723372.2737784 2015

  7. [7]

    Adam Bellemare. 2020. Building Event-Driven Microservices: Leveraging Organi- zational Data at Scale . O’Reilly Media, Sebastopol, CA

    work page 2020

  8. [8]

    Phil Bernstein. 2025. New query functionality #4232 . Retrieved April 23, 2025 from https://github.com/dotnet/orleans/issues/4232

    work page 2025

  9. [9]

    Bernstein, Vassos Hadzilacos, and Nathan Goodman

    Philip A. Bernstein, Vassos Hadzilacos, and Nathan Goodman. 1987.Concurrency Control and Recovery in Database Systems . Addison-Wesley

    work page 1987

  10. [10]

    Meiklejohn, and Xiangfeng Zhu

    Sebastian Burckhardt, Badrish Chandramouli, Chris Gillum, David Justo, Kon- stantinos Kallas, Connor McMahon, Christopher S. Meiklejohn, and Xiangfeng Zhu. 2022. Netherite: efficient execution of serverless workflows. Proc. VLDB Endow. 15, 8 (April 2022), 1591–1604. https://doi.org/10.14778/3529337.3529344

    work page doi:10.14778/3529337.3529344 2022

  11. [11]

    Sergey Bykov, Alan Geller, Gabriel Kliot, Jim Larus, Ravi Pandya, and Jorgen Thelin. 2010. Orleans: A Framework for Cloud Computing . Technical Report MSR- TR-2010-159. https://www.microsoft.com/en-us/research/publication/orleans- a-framework-for-cloud-computing/

    work page 2010

  12. [12]

    Jon Chew. 2019. A voiding Double Payments in a Distributed Payments System . AirBnb. Retrieved April 8, 2024 from https://medium.com/airbnb-engineering/ avoiding-double-payments-in-a-distributed-payments-system-2981f6b070bb

    work page 2019

  13. [13]

    Dmitry Chornyi. 2018. Engineering Uber’s Next-Gen Payments Platform. Uber Technologies Inc. Retrieved April 8, 2024 from https://eng.uber.com/payments- platform

    work page 2018

  14. [14]

    Ship It and See What Happens

    Dan Conger. 2021. How Apache Kafka Enables Podium to “Ship It and See What Happens”. Confluent. Retrieved April 8, 2024 from https://www.confluent.io/ blog/how-apache-kafka-enables-podium-to-ship-it-and-see-what-happens

    work page 2021

  15. [15]

    The Transaction Processing Council. [n.d.]. TPC-C Benchmark (Revision 5.9.0) . Retrieved October, 15 2024 from http://www.tpc.org/tpcc

    work page 2024

  16. [16]

    Dapr. [n.d.]. Dapr SDK for .NET . Retrieved November, 4 2024 from https: //github.com/dapr/dotnet-sdk

    work page 2024

  17. [17]

    Dapr. [n.d.]. Dependency graph – Dapr SDK for .NET . Retrieved November, 4 2024 from https://github.com/dapr/dotnet-sdk/network/dependents

    work page 2024

  18. [18]

    Dapr. 2024. Dapr is a portable, event-driven, runtime for building distributed applications across cloud and edge . Retrieved October, 16 2024 from https: //github.com/dapr/dapr

    work page 2024

  19. [19]

    Dapr. 2024. Distributed Application Runtime. Retrieved October, 16 2024 from https://dapr.io/

    work page 2024

  20. [20]

    Dapr. 2024. Workflow overview. Retrieved October, 16 2024 from https://docs.dapr. io/developing-applications/building-blocks/workflow/workflow-overview/

    work page 2024

  21. [21]

    Dapr Docs. [n.d.]. Redis Streams . Microsoft. Retrieved October, 16 2024 from https://docs.dapr.io/reference/components-reference/supported-pubsub/ setup-redis-pubsub/

    work page 2024

  22. [22]

    Rafael Ferreira. 2019. Microservices at Nubank, an overview . Nubank. Retrieved April 8, 2024 from https://building.nubank.com.br/microservices-at-nubank-an- overview

    work page 2019

  23. [23]

    Rafael Ferreira and Edward Wible. 2017. Architecting a Modern Financial Institu- tion. Nubank. Retrieved April 8, 2024 from https://www.infoq.com/presentations/ nubank-architecture

    work page 2017

  24. [24]

    Martin Fowler. [n.d.]. Repository. Retrieved January, 3 2024 from https:// martinfowler.com/eaaCatalog/repository.html

    work page 2024

  25. [25]

    Martin Fowler. [n.d.]. Service Layer . Retrieved January, 3 2024 from https: //martinfowler.com/eaaCatalog/serviceLayer.html

    work page 2024

  26. [26]

    Martin Fowler. 2004. Inversion of Control Containers and the Dependency Injection pattern. http://martinfowler.com/articles/injection.html

    work page 2004

  27. [27]

    The Computer Language 25.03 Benchmarks Game. 2025. C# versus Java. Re- trieved April 23, 2025 from https://benchmarksgame-team.pages.debian.net/ benchmarksgame/fastest/csharpcore-javavm.html

    work page 2025

  28. [28]

    Hector Garcia-Molina and Kenneth Salem. 1987. Sagas. In Proceedings of the 1987 ACM SIGMOD International Conference on Management of Data (San Francisco, California, USA) (SIGMOD ’87). Association for Computing Machinery, New York, NY, USA, 249–259. https://doi.org/10.1145/38713.38742

    work page doi:10.1145/38713.38742 1987

  29. [29]

    Adam Gluck. 2022. Introducing Domain-Oriented Microservice Architecture. Uber Technologies Inc. Retrieved April 8, 2024 from https://www.uber.com/en-DK/ blog/microservice-architecture

    work page 2022

  30. [30]

    Jonathan Goldstein, Ahmed Abdelhamid, Mike Barnett, Sebastian Burckhardt, Badrish Chandramouli, Darren Gehring, Niel Lebeck, Christopher Meiklejohn, Umar Farooq Minhas, Ryan Newton, Rahee Ghosh Peshawaria, Tal Zaccai, and Irene Zhang. 2020. A.M.B.R.O.S.I.A: providing performant virtual resiliency for distributed applications. Proc. VLDB Endow. 13, 5 (Jan....

    work page doi:10.14778/3377369.3377370 2020

  31. [31]

    Graefe and W.J

    G. Graefe and W.J. McKenna. 1993. The Volcano optimizer generator: extensibility and efficient search. In Proceedings of IEEE 9th International Conference on Data Engineering. 209–218. https://doi.org/10.1109/ICDE.1993.344061

    work page doi:10.1109/icde.1993.344061 1993

  32. [32]

    Pat Helland. 2015. Immutability Changes Everything. Commun. ACM 59, 1 (Dec. 2015), 64–70. https://doi.org/10.1145/2844112

    work page doi:10.1145/2844112 2015

  33. [33]

    Pat Helland. 2020. Data on the outside versus data on the inside. Commun. ACM 63, 11 (2020), 111–118. https://doi.org/10.1145/3410623

    work page doi:10.1145/3410623 2020

  34. [34]

    Gregor Hohpe and Bobby Woolf. 2004. Event-Driven Architecture: How SOA Enables the Real-Time Enterprise. Addison-Wesley Professional, Boston, MA

    work page 2004

  35. [35]

    Sambasivan

    Darby Huye, Yuri Shkuro, and Raja R. Sambasivan. 2023. Lifting the veil on Meta’s microservice architecture: Analyses of topology and request workflows. In 2023 USENIX Annual Technical Conference (USENIX ATC 23) . USENIX Association, Boston, MA, 419–432. https://www.usenix.org/conference/atc23/presentation/ huye

    work page 2023

  36. [36]

    Ninad Khisti. 2018. Measuring Transactional Integrity in Airbnb’s Dis- tributed Payment Ecosystem . AirBnb. Retrieved April 8, 2024 from https://medium.com/airbnb-engineering/measuring-transactional-integrity- in-airbnbs-distributed-payment-ecosystem-a670d6926d22

    work page 2018

  37. [37]

    Beresford, and Boerge Svingen

    Martin Kleppmann, Alastair R. Beresford, and Boerge Svingen. 2019. Online Event Processing: Achieving Consistency Where Distributed Transactions Have Failed. Queue 17, 1 (2019), 116–136

    work page 2019

  38. [38]

    Jay Kreps, Neha Narkhede, Jun Rao, et al. 2011. Kafka: A distributed messaging system for log processing. In Proceedings of the NetDB , Vol. 11. Athens, Greece, 1–7

    work page 2011

  39. [39]

    Rodrigo Laigner, Zhexiang Zhang, Yijian Liu, Leonardo Freitas Gomes, and Yongluan Zhou. 2025. Online Marketplace: A Benchmark for Data Management in Microservices. Proc. ACM Manag. Data 3, 1, Article 3 (Feb. 2025), 26 pages. https://doi.org/10.1145/3709653

    work page doi:10.1145/3709653 2025

  40. [40]

    Rodrigo Laigner, Yongluan Zhou, Marcos Antonio Vaz Salles, Yijian Liu, and Marcos Kalinowski. 2021. Data Management in Microservices: State of the Practice, Challenges, and Research Directions. Proc. VLDB Endow. 14, 13 (sep 2021), 3348–3361. https://doi.org/10.14778/3484224.3484232

    work page doi:10.14778/3484224.3484232 2021

  41. [41]

    Tianyu Li, Badrish Chandramouli, Sebastian Burckhardt, and Samuel Madden

    work page

  42. [42]

    DARQ Matter Binds Everything: Performant and Composable Cloud Programming via Resilient Steps. Proc. ACM Manag. Data 1, 2, Article 117 (June 2023), 27 pages. https://doi.org/10.1145/3589262

    work page doi:10.1145/3589262 2023

  43. [43]

    Yijian Liu, Rodrigo Laigner, and Yongluan Zhou. 2024. Rethinking State Man- agement in Actor Systems for Cloud-Native Applications. In Proceedings of the 2024 ACM Symposium on Cloud Computing (Redmond, WA, USA) (SoCC ’24). Association for Computing Machinery, New York, NY, USA, 898–914. https://doi.org/10.1145/3698038.3698540

    work page doi:10.1145/3698038.3698540 2024

  44. [44]

    Yijian Liu, Li Su, Vivek Shah, Yongluan Zhou, and Marcos Antonio Vaz Salles

    work page

  45. [45]

    In SIGMOD ’22: International Conference on Management of Data, Philadelphia, PA, USA, June 12 - 17, 2022

    Hybrid Deterministic and Nondeterministic Execution of Transactions in Actor Systems. In SIGMOD ’22: International Conference on Management of Data, Philadelphia, PA, USA, June 12 - 17, 2022 . ACM, 65–78. https://doi.org/10.1145/ 3514221.3526172

    work page arXiv 2022

  46. [46]

    Shutian Luo, Huanle Xu, Chengzhi Lu, Kejiang Ye, Guoyao Xu, Liping Zhang, Yu Ding, Jian He, and Chengzhong Xu. 2021. Characterizing Microservice Dependency and Performance: Alibaba Trace Analysis. In Proceedings of the ACM Symposium on Cloud Computing (Seattle, WA, USA)(SoCC ’21). Association for Computing Machinery, New York, NY, USA, 412–426. https://do...

    work page arXiv 2021

  47. [47]

    Ricardo Mayerhofer. 2018. restQL: Tackling microservice query complexity . B2W. Retrieved April 8, 2024 from https://medium.com/b2w-engineering-en/restql- tackling-microservice-query-complexity-27def5d09b40

    work page 2018

  48. [48]

    Microsoft. 2023. Language Integrated Query (LINQ) . Retrieved January, 1 2025 from https://learn.microsoft.com/en-us/dotnet/csharp/linq

    work page 2023

  49. [49]

    John Nagle. [n.d.]. Congestion Control in IP/TCP Internetworks . Retrieved De- cember, 24 2024 from https://datatracker.ietf.org/doc/html/rfc896

    work page 2024

  50. [50]

    Faisal Nawab and Mohammad Sadoghi. 2023. Consensus in Data Management: From Distributed Commit to Blockchain . Vol. 12. Foundations and Trends ® in Databases. 221–364 pages. https://doi.org/10.1561/1900000075

    work page doi:10.1561/1900000075 2023

  51. [51]

    Matheus Oliveira. 2017. Gerenciamento de dados com micro-serviços e a experiência do iFood . iFood. Retrieved April 8, 2024 from https://www.infoq.com/br/presentations/gerenciamento-de-dados-com- micro-servicos-e-a-experiencia-do-ifood

    work page 2017

  52. [52]

    Diego Ongaro and John Ousterhout. 2014. In Search of an Understandable Consensus Algorithm. In 2014 USENIX Annual Technical Conference (USENIX ATC 14). USENIX Association, Philadelphia, PA, 305–319. https://www.usenix. Rodrigo Laigner and Yongluan Zhou org/conference/atc14/technical-sessions/presentation/ongaro

    work page 2014

  53. [53]

    OpenJDK. [n.d.]. More New I/O APIs for the Java Platform . Retrieved January, 17 2025 from https://openjdk.org/projects/nio/

    work page 2025

  54. [54]

    Oracle. 2013. Introduction to the Java Persistence API . Retrieved November, 4 2024 from https://docs.oracle.com/javaee/6/tutorial/doc/bnbpz.html

    work page 2013

  55. [55]

    Oracle. 2014. Java JDBC API . Retrieved November, 4 2024 from https://docs. oracle.com/javase/8/docs/technotes/guides/jdbc/

    work page 2014

  56. [56]

    Oracle. 2024. Java Native Interface Specification—Contents . Retrieved October, 16 2024 from https://docs.oracle.com/javase/7/docs/technotes/guides/jni/spec/ intro.html

    work page 2024

  57. [57]

    Orleans. [n.d.]. Best Practices. Retrieved October, 15 2024 from https://dotnet. github.io/orleans/docs/resources/best_practices.html

    work page 2024

  58. [58]

    Orleans. 2024. Grain persistence . Retrieved April 23, 2025 from https://learn.microsoft.com/en-us/dotnet/orleans/grains/grain-persistence/ ?pivots=orleans-7-0

    work page 2024

  59. [59]

    Orleans. 2025. Cluster management in Orleans . Retrieved April 23, 2025 from https://learn.microsoft.com/en-us/dotnet/orleans/implementation/cluster- management

    work page 2025

  60. [60]

    Microsoft Orleans. [n.d.]. Streaming with Orleans. Microsoft. Retrieved January, 3 2024 from https://learn.microsoft.com/en-us/dotnet/orleans/streaming/?pivots= orleans-7-0

    work page 2024

  61. [61]

    Xi Pang and Jianguo Wang. 2024. Understanding the Performance Implications of the Design Principles in Storage-Disaggregated Databases. In Proceedings of ACM Conference on Management of Data (SIGMOD)

    work page 2024

  62. [62]

    David Pine. 2025. Load balancing. Retrieved April 23, 2025 from https://learn. microsoft.com/en-us/dotnet/orleans/implementation/load-balancing

    work page 2025

  63. [63]

    Dan Pritchett. 2008. Base: An Acid Alternative. In File Systems and Storage, Vol. 6. ACM Queue. Issue 3

    work page 2008

  64. [64]

    Redis. [n.d.]. Redis Streams. Retrieved October, 16 2024 from https://redis.io/ docs/latest/develop/data-types/streams/

    work page 2024

  65. [65]

    Redis. 2020. . Retrieved January, 1 2025 from https://redis.io/blog/diving-into- redis-6

    work page 2020

  66. [66]

    Nitin Sarma. 2020. Event Driven Architectures @ Netflix Content Finance Engineer- ing. Netflix. Retrieved April 8, 2024 from https://www.linkedin.com/pulse/event- driven-architectures-netflix-content-finance-engineering-s/

    work page 2020

  67. [67]

    Natan Silnitsky. 2022. Event Driven Architecture — 5 Pitfalls to A void . Wix. Retrieved July 1, 2023 from https://medium.com/wix-engineering/event-driven- architecture-5-pitfalls-to-avoid-b3ebf885bdb1

    work page 2022

  68. [68]

    Natan Silnitsky. 2022. Troubleshooting Kafka for 2000 Microservices at Wix . Wix. Retrieved July 1, 2023 from https://medium.com/wix-engineering/ troubleshooting-kafka-for-2000-microservices-at-wix-986ee382fd1e

    work page 2022

  69. [69]

    Aakriti Singla and Simon Wu. 2020. Revolutionizing Money Movements at Scale with Strong Data Consistency . Uber Technologies Inc. Retrieved April 8, 2024 from https://eng.uber.com/money-scale-strong-data

    work page 2020

  70. [70]

    CAE Specification. 1991. Distributed Transaction Processing: the XA Specification . X/Open

    work page 1991

  71. [71]

    Apache Flink Statefun. 2023. Stateful Functions: A Platform-Independent Stateful Serverless Stack. Retrieved November 11, 2023 from https://nightlies.apache.org/ flink/flink-statefun-docs-master/

    work page 2023

  72. [72]

    Jan Stenberg. 2019. Experiences Moving from Microservices to Workflows at Jet.com. Jet.com. Retrieved March 21, 2024 from https://www.infoq.com/news/2019/02/ migrate-microservices-workflows

    work page 2019

  73. [73]

    Tanenbaum and Maarten van Steen

    Andrew S. Tanenbaum and Maarten van Steen. 2016. Distributed Systems: Princi- ples and Paradigms (2nd ed.). CreateSpace Independent Publishing Platform

    work page 2016

  74. [74]

    Chuzhe Tang, Zhaoguo Wang, Xiaodong Zhang, Qianmian Yu, Binyu Zang, Haibing Guan, and Haibo Chen. 2022. Ad Hoc Transactions in Web Ap- plications: The Good, the Bad, and the Ugly. In Proceedings of the 2022 In- ternational Conference on Management of Data (Philadelphia, PA, USA) (SIG- MOD ’22). Association for Computing Machinery, New York, NY, USA, 4–18....

    work page doi:10.1145/3514221.3526120 2022

  75. [75]

    Alexander Thomson, Thaddeus Diamond, Shu-Chun Weng, Kun Ren, Philip Shao, and Daniel J. Abadi. 2012. Calvin: fast distributed transactions for par- titioned database systems. In Proceedings of the 2012 ACM SIGMOD Interna- tional Conference on Management of Data (Scottsdale, Arizona, USA) (SIG- MOD ’12). Association for Computing Machinery, New York, NY, U...

    work page doi:10.1145/2213836.2213838 2012

  76. [76]

    Nicolas Viennot, Mathias Lécuyer, Jonathan Bell, Roxana Geambasu, and Jason Nieh. 2015. Synapse: A Microservices Architecture for Heterogeneous-Database Web Applications. In Proceedings of the Tenth European Conference on Computer Systems (Bordeaux, France) (EuroSys ’15). Association for Computing Machin- ery, New York, NY, USA, Article 21, 16 pages. http...

    work page doi:10.1145/2741948 2015

  77. [77]

    Yiwen Wang, Júlio Cesar dos Reis, Kasper Myrtue Borggren, Marcos Antonio Vaz Salles, Claudia Bauzer Medeiros, and Yongluan Zhou. 2019. Modeling and Build- ing IoT Data Platforms with Actor-Oriented Databases. In Advances in Database Technology - 22nd International Conference on Extending Database Technology, EDBT 2019, Lisbon, Portugal, March 26-29, 2019 ...

    work page doi:10.5441/002/edbt.2019.47 2019

  78. [78]

    Yingjun Wu, Joy Arulraj, Jiexi Lin, Ran Xian, and Andrew Pavlo. 2017. An empirical evaluation of in-memory multi-version concurrency control. Proc. VLDB Endow. 10, 7 (March 2017), 781–792. https://doi.org/10.14778/3067421. 3067427

    work page doi:10.14778/3067421 2017

  79. [79]

    Yang Yang, Zhifeng Chen, Qichao Chu, Haitao Zhang, and George Teo. 2021. Enabling Seamless Kafka Async Queuing with Consumer Proxy. Uber Technologies Inc. Retrieved April 8, 2024 from https://www.uber.com/en-SE/blog/kafka- async-queuing-with-consumer-proxy/

    work page 2021

  80. [80]

    Haoran Zhang, Konstantinos Kallas, Spyros Pavlatos, Rajeev Alur, Sebastian Angel, and Vincent Liu. 2024. MuCache: A General Framework for Caching in Microservice Graphs. In 21st USENIX Symposium on Networked Systems Design and Implementation (NSDI 24) . USENIX Association, Santa Clara, CA, 221–238. https://www.usenix.org/conference/nsdi24/presentation/zha...

    work page 2024

Showing first 80 references.