Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for Azure #22

Open
HansKristianVikOlsen opened this issue Feb 9, 2023 · 1 comment
Open

Support for Azure #22

HansKristianVikOlsen opened this issue Feb 9, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@HansKristianVikOlsen
Copy link

I still haven't seen any implementation with azure that is based on the fourkeys. Do you know any yourself? Would it easy to change this and add it?

Thanks! :)

@mikaelvesavuori
Copy link
Owner

mikaelvesavuori commented Feb 15, 2023

Hey! Sorry about the delay in responding @HansKristianVikOlsen.

I'm only finding various commercial offerings, which is a bit of the reason I made this, so unfortunately not that many options out there if you are looking for open source – at least that I know of!

When it comes to supporting more platforms my thoughts would be to start with the obvious missing/changing parts:

  • The code is fairly well segmented and not (itself) tightly coupled to much more than the handler function.
  • Ergo: Supporting for example Azure would require an additional, new, handler function that uses the corresponding Azure handler format (not too different, but still not the same).
  • We would probably want to add a dedicated serverless.yml with the Azure configuration given that a) it's not AWS, b) the format/provider is different, c) we would need to set up other infra (i.e. exclude AWS Gateway and change to, for example, CosmosDB)
  • We need to add an additional repository (CosmosDB?) implementing the Repository interface (https://github.com/mikaelvesavuori/dorametrix/blob/main/src/interfaces/Repository.ts).
  • Going to Azure might mean we need to rethink the use of the authorizer function, and change/remove the API Gateway to API Management.
  • I thoroughly dislike working with Azure Functions, especially in Serverless Framework, as the support has been really bad previously. It might be relevant to support another IaC tool in the Azure case, but of course: The more deviation, the less we can package these together in the same package without unnecessary bloat and pain.

Hope that gives some ideas – but yeah, it should be completely doable!

@mikaelvesavuori mikaelvesavuori added the enhancement New feature or request label Feb 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants