Thanks for sharing this. Really interesting. But a basic question, why not upgrading to PG 13 instead? I am curious about the reasons for staying on an older version of PostgreSQL.
If AWS is an option for you, take a look at the AWS Serverless ecosystem, particularly Lambda, Eventbridge, and API GW. I have worked with these (and other services) for large projects, and they work great, especially for Node.js based applications. Aurora Serverless V2 looks promising too, but I didn't have a chance to work with it yet, only RDS and DynamoDB.
It's getting better and better, and with a predictive ML model, it can become invisible for most use cases. Unfortunately, cloud Run has an even longer startup time if you need to span more "instances" in response to spikes in traffic, so Cloud Run doesn't fix the cold start yet.
That's an insightful article. Thanks for sharing. I still prefer the whole (logical) approach of having VM/Container/Unikernel per execution. FaaS isolates misbehaved calls/payloads from other calls. It also makes rolling out new versions easier, as it will handle ANY new call to your function. AWS has reduced Lambda's cold start a lot in the last years, but Cloud functions still have a long cold start-up time and not the best performance. I think it's a matter of time for FaaS to become the first choice for computing for most enterprise projects.
Is there any migration scenario that you anticipate your view strategy won't be able to handle? Maybe add a "Limitations" section? Again..congrats. I am impressed and I hope someday this becomes part of PostgreSQL native feature set.
Wow! I love how elegant and powerful your strategy is. There is a lot of potential here and your tool might turn PostgreSQL into an even easier choice for new projects. Congratulations!
Congrats to the Angular team and its community. I think Angular is closer to Next.js than it is to React.js. I am excited to see all this progress on this front. What a time to be alive!
I am a PostgreSQL enthusiast (neither a developer nor a DBA, though), and I am always surprised by the number of capabilities PostgreSQL (and the community) offers. It's a true DATA ecosystem.
Hey people, first, congrats for the great work on GCC for RUST, second I have a basic question here from someone who is not experienced with low level languages. Would it be possible (and beneficial to the community) to have a "compiler as a service" in the cloud (either GCC or LLVM based) that would have the most powerful hardware setup available to compile RUST? Really cheap/free per seconds of compilation... so anyone would be able to compile Rust faster and also ANY improvement would de added to this Service... and once new and more powerful hardware is available it could be shared and used by the community. I know we still have to work on improving the compilation times, but maybe having a shared compilation pipeline that can be used by everyone could somehow alleviate the pain a little. Thanks
I am completely new to PL/pgSQL, so forgive me for the BASIC question, but (out of curiosity) for string manipulation is PL/pgSQL too slow compared to modern LUA/Python? The function that I have in mind will get a TEXT and return another TEXT with the PHONETIC representation of this TEXT.
It's not a limitation that affects most of users, but lack of official multi master support makes it less suitable for "always on" databases. But to be honest multi master is something hard to get right in ANY database. PostgreSQL is great for many use cases and good enough for many more!
- Security;
- More suitable for Serverless deployment (like running a full server on V8 Isolates) - Cloud Workers and Fastly (0ms cold starts)... check this out -> https://deno.com/blog/deploy-beta1
- Embraces Typescript as a first class citizen.
Congratulations! .NET is increasing the lead. It was already (generally) faster than JVM. One thing that I find really crucial is the COLD START times, this is a super important factor when using .NET as a primary platform for FaaS (Serverless Architecture), like Lambda, Azure and Google Functions. I think that's an important characteristic of languages VMs for the next years.
Not 100% related, but can the editing capability be (strongly) protected by login/password (Microsoft AD, for instance) so that only authorized users are able to edit the website?
The biggest difference is the COLD START, Google offering being in a different ball park. AWS sports ˜300ms cold starts (node and python) while GCP (and Azure) take 5 ~ 10 seconds. I hope GCP catches up or surpass AWS in the near future, but the gap today is HUGE. Price is quite similar if you don't hit Cold Start invocations very frequently.
Would it be able to apply some (most) of these technics to other RDBMS like PostgreSQL and MySQL? Maybe some of (non private/secure) information about the queries/stats could be sent back to a centralised server that would be ingested by the ML model making it even "smarter".