I have two different applications Build with Hasura as the backend and I would like both of them to use the same Postgres instance. Would I encounter any difficulties making this happen? Is it even possible? And what do I need to take into account while running my apps this way?
Both apps have different code bases, use different tables and are run from diffferent docker images.
Different Hasura apps can be configured to use the same backend. It's possible. For postgres its simply multiple clients trying to access data. Since you said they use different tables, it makes things simpler.
Related
I have a CI/DC pipeline with google cloud build triggers that deploy my code to different sites depending on which branch I push to. The develop site is a live test - the final check before I merge to master, which triggers a deploy of master to the production site.
Currently, both sites use the same firebase Firestore db, and any document changed on the develop site will also be changed on the production site.
What I want to avoid is creating another firebase project to push the develop code to with a different database, because that means I need a separate set of credentials and would copy the same functions over to the new project every time I change them. That's not maintainable and is a lot of work.
What I would like is some way for the develop site to only have access to part of the firestore database, and the production site to have access to another part.
How do people do this? Is it even possible? Is there a better way? One alternative I can think of is using authentication and creating separate accounts for testing with different access permissions, but this seems a work-around and not the ideal solution.
What you're trying to do sounds like a lot more hassle than using multiple projects, which is the documented and strongly preferred solution. Putting everything in one project is a huge anti-pattern in Firebase and Google Cloud, and it will cause you more problems in the long run, in addition to increasing the risk of catastrophic failure if you manage to misconfigure something in that one project.
It's perfectly maintainable to have multiple projects like this, if you apply some scripting to automate the work. This is very common, and I strongly suggest thinking through how this would work for you.
You CI/CD pipeline could definitely check out your updates from source control and deploy them to whatever other project environments you have set up. It's very common to manage different credentials and configurations for use in CI/CD.
I want to run two different scripts in one database.
How can i maintain two seperate versions for these scripts? We have such requirement because these two scripts belong to two different modules.and we have to run them different times.I need to implement this in API java.
Can anybody help me???
Run Flyway twice, each time with a different setting for flyway.table. Just be aware that clean will not differentiate and clean the whole schema.
I'd like to deploy the same app at a couple different locations, and perhaps also in different versions, and I'd like all my deployments to run off the same Mongo database. Are there any pitfalls to taking this approach?
Just have them use the same MONGO_URL and it will work fine. Also see this question. We do exactly that and have not encountered any problems.
If you are running in multiple physical locations, keep in mind that mongodb traffic isn't sent over https. For this reason, the current best practice is to host your database and your app in the same in the same data center (e.g. use compose.io and host in EC2 east).
I'm very new to BizTalk. I have a problem here:
Both PC12-4 and PC12-0 are working on the same project at the same time. If they change code and do test at the same time, the result will be affected by each other. From http://msdn.microsoft.com/en-us/library/aa561042.aspx I noticed that it's not recommended to have multiple host instances in one host.
I wonder is there any way to allow the result not affected? The aim is for multiple people working and testing the same program at the same time. Because we finished one part of the application and the users want to test it now while we are doing the second part. The users test results are affected by our new changes.
Many thanks!
If I interpret you situation correctly, the problem is not with the Host/Instance configuration, rather, what you are trying to do, use PC12-4 and PC12-0 for the same project but different purposes, DEV and TEST, is not supported.
Meaning, you can't have different versions of the same app installed on two different servers in the same Group. There is no way around this and there is no way to make it work in the way you want. Sorry.
What you need to do is split PC12-4 and PC12-0 into two separate BizTalk Groups, meaning two separate sets of SQL Server databases in two separate instances of SQL Server. One Group for DEV and the other for user TEST.
But, even then, you may still have problems because multiple developers sharing a single BizTalk Group/Server is not workable scenario. Each developer should have their own full stack, Windows, SQL Server, BizTalk Server and Visual Studio. The best way to achieve this is dedicated developer VM's.
I have a local and an azure ASP.NET Membership database. I need to be sync them both. Wondering if anyone has found a easy way to do this? The table structure seems simple enough but would rather pull from azure than push. Is there a routine or tool I do not know about to do this by now?
Thanks
-Ken
This would be a suitable job for the Microsoft Sync Framework.
You create a service or scheduled task that makes the necessary calls. Have this running on your server and you can pull from the Azure database and sync with the local one. It can be set up to sync one way or two ways.