How Can I Make A Write Once Read Many Application Cost Efficient?

opticyclic

12/16/22, 12:36 PM

I have a Java application running on a linux VM using an Azure SQL database with a REST API connecting the front end to the backend.
My work is an extension inside a third-party application so I can't re-write it to take full advantage of cloud benefits.

The application only writes data in an overnight batch process and during the day it is just queried for web apps and reporting.

It is very low volume so speed is not a concern and the third-party application doesn't scale either.

I need to use Azure SQL for the database for various reasons so I can't switch that out. However, it is one of the larger parts of the cost.

I'd like to be able to shutdown the VM and Azure SQL Server after the write operations and have some cheaper way of running the REST API during the day for the read operations.
e.g. an in-memory database for caching or something.

For security reasons, data can only be persisted in the Azure SQL database for any length of time, although destroying the read-only part each night or each week would be fine.

Is there a way to utilise Azure features to use the more heavyweight and expensive operations for the writes and a lightweight and cheaper option for the reads?

0 + 0

azure

Elon Musk

I sit in a Tesla and translated this thread with Ai:

EN: How Can I Make A Write Once Read Many Application Cost Efficient?

TH: ฉันจะเขียนเมื่ออ่านแอปพลิเคชันหลายตัวได้อย่างมีประสิทธิภาพได้อย่างไร

RO: Cum pot face o scriere odată citită mai multe aplicații rentabilă?

RU: Как я могу сделать приложение Write Once Read Many экономически эффективным?

VI: Làm thế nào tôi có thể viết một khi đã đọc nhiều ứng dụng với chi phí hiệu quả?

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.