The AWS solution architects are worried about latency, and I'm worried that the "chatty protocol" will makes things worse. They are suggesting we go over to MySQL (which I would prefer to avoid at all costs if possible). Have there been further improvements to this since Firebird 2.1 that aren't mentioned in the FAQ? |
Has anyone else had experience hosting Firebird on AWS? Any findings or advice? I'm wondering if I somehow manage to stick to using AWS features hosted all in the same city's same datacentre, then I might be able to get away without any major latency issues. |
Hello,
I think You have to use some kind of root server or a virtual server in the internet.
We have also some Firebird databases behind a REST web service. We have our own web server and also a Firebird database server “behind” this web server. But You can host a web server and a database server on the same (virtual) machine.
This means the web server will hosts the REST web service and is available via an URL over the internet (public IP). The database server is only available via the web server (web server has two different IPs) and is located in the same (internal) LAN as the web server. The communication (REST web service <-> Firebird Database) is as fast as in a “normal” Client Server environment.
Unfortunately I have no experience with AWS/Azure.
Regards
Mathias
--
You received this message because you are subscribed to the Google Groups "firebird-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
firebird-suppo...@googlegroups.com.
To view this discussion on the web, visit
https://groups.google.com/d/msgid/firebird-support/b05340a4-5412-4f0a-b39b-6c5da38f688cn%40googlegroups.com.
Have there been further improvements to this since Firebird 2.1 that aren't mentioned in the FAQ?
>Look this: https://www.firebirdnews.org/firebird-3-protocol-benchmark/
Has anyone else had experience hosting Firebird on AWS? Any findings or advice? I'm wondering if I somehow manage to stick to using AWS features hosted all in the same city's same datacentre, then I might be able to get away without any major latency issues.
>>I know people in Brazil running FB 3 on AWS using standard Client/Server mode and they are very happy with the result. I guess you will be ok if you avoid unnecessary blob transfers. Also, choose an Amazon datacenter location that gives the lowest latency to your customers.
We have also some Firebird databases behind a REST web service. We have our own web server and also a Firebird database server “behind” this web server. But You can host a web server and a database server on the same (virtual) machine.
This means the web server will hosts the REST web service and is available via an URL over the internet (public IP). The database server is only available via the web server (web server has two different IPs) and is located in the same (internal) LAN as the web server. The communication (REST web service <-> Firebird Database) is as fast as in a “normal” Client Server environment.
It should be possible to implement this on AWS by running Firebird on an EC2 instance in a VPC (AWS VPN) with the Lambda function/API gateways etc implementing the serverless application. The AWS solution architects should know how to get that working.
Hamish