Need advice about which tool to choose?Ask the StackShare community!
Azure Functions vs Flyway: What are the differences?
<Write Introduction here>
Integration with Microsoft Azure: Azure Functions is a serverless compute service that enables you to run event-triggered code without having to explicitly provision or manage infrastructure. On the other hand, Flyway is an open-source database migration tool that allows for version control and automated deployment of database schema changes.
Primary Use Case: Azure Functions are primarily used for building event-driven solutions and microservices, allowing developers to focus on writing code without the need to worry about managing servers. Meanwhile, Flyway is designed specifically for managing database schema changes, making it ideal for DevOps teams working on database-related projects.
Scalability: Azure Functions can automatically scale based on demand, meaning that resources are dynamically allocated to handle increases in workload. In contrast, Flyway does not have built-in scalability features as it is focused on managing database migrations in a controlled manner.
Programming Languages Supported: Azure Functions support a wide range of programming languages including C#, Java, JavaScript, Python, and PowerShell, providing flexibility for developers to choose the language they are most comfortable with. In comparison, Flyway is language-agnostic and can be used with any database that supports JDBC, making it versatile but not tied to specific programming languages.
Deployment Strategy: Azure Functions are typically deployed as individual functions within a serverless application, allowing for easy deployment and management of discrete units of code. Flyway, on the other hand, is usually integrated into the deployment pipeline of a database project, ensuring that database schema changes are applied consistently across different environments.
Cost Model: Azure Functions follow a consumption-based pricing model, where users are charged based on the number of executions and resources consumed by their functions. In contrast, Flyway is open-source and free to use, with optional commercial support available for enterprise customers.
In Summary, Azure Functions and Flyway differ in their integration with Microsoft Azure, primary use case, scalability, programming languages supported, deployment strategy, and cost model.
Need advice on what platform, systems and tools to use.
Evaluating whether to start a new digital business for which we will need to build a website that handles all traffic. Website only right now. May add smartphone apps later. No desktop app will ever be added. Website to serve various countries and languages. B2B and B2C type customers. Need to handle heavy traffic, be low cost, and scale well.
We are open to either build it on AWS or on Microsoft Azure.
Apologies if I'm leaving out some info. My first post. :) Thanks in advance!
I recommend this : -Spring reactive for back end : the fact it's reactive (async) it consumes half of the resources that a sync platform needs (so less CPU -> less money). -Angular : Web Front end ; it's gives you the possibility to use PWA which is a cheap replacement for a mobile app (but more less popular). -Docker images. -Kubernetes to orchestrate all the containers. -I Use Jenkins / blueocean, ansible for my CI/CD (with Github of course) -AWS of course : u can run a K8S cluster there, make it multi AZ (availability zones) to be highly available, use a load balancer and an auto scaler and ur good to go. -You can store data by taking any managed DB or u can deploy ur own (cheap but risky).
You pay less money, but u need some technical 2 - 3 guys to make that done.
Good luck
My advice will be Front end: React Backend: Language: Java, Kotlin. Database: SQL: Postgres, MySQL, Aurora NOSQL: Mongo db. Caching: Redis. Public : Spring Webflux for async public facing operation. Admin api: Spring boot, Hibrernate, Rest API. Build Container image. Kuberenetes: AWS EKS, AWS ECS, Google GKE. Use Jenkins for CI/CD pipeline. Buddy works is good for AWS. Static content: Host on AWS S3 bucket, Use Cloudfront or Cloudflare as CDN.
Serverless Solution: Api gateway Lambda, Serveless Aurora (SQL). AWS S3 bucket.
Pros of Azure Functions
- Pay only when invoked14
- Great developer experience for C#11
- Multiple languages supported9
- Great debugging support7
- Can be used as lightweight https service5
- Easy scalability4
- WebHooks3
- Costo3
- Event driven2
- Azure component events for Storage, services etc2
- Poor developer experience for C#2
Pros of Flyway
- Superb tool, easy to configure and use13
- Very easy to config, great support on plain sql scripts9
- Is fantastic and easy to install even with complex DB6
- Simple and intuitive4
- Easy tool to implement incremental migration1
Sign up to add or upvote prosMake informed product decisions
Cons of Azure Functions
- No persistent (writable) file system available1
- Poor support for Linux environments1
- Sporadic server & language runtime issues1
- Not suited for long-running applications1
Cons of Flyway
- "Undo Migrations" requires pro version, very expensive3
