4 ms·

This is amazing. Could you elaborate on the "No vendor lock-in" part? When we select cloud services like Heroku or AWS, aren't we technically locked-in? For e

by frx 5y ago

This is amazing. Could you elaborate on the "No vendor lock-in" part? When we select cloud services like Heroku or AWS, aren't we technically locked-in? For example, AWS Amplify will create DNS entries and its own SSL certificate for the domain. If we wanted to switch, we'll have to set these up again in the new provider. How does Molecule not make you locked-in to the providers you select?

lowercased 5y ago
i take it to mean you're not locked in to molecule directly.
- loh 5y ago
  Yes, this is also the case. (Referencing my sibling reply.)
loh 5y ago
Great question. As it is now, Molecules are designed to be as independent (platform/vendor agnostic) and flexible as possible. For example, when I was trying out all the different cloud services myself, I was able to connect each of them to my git repository, and they would each build and deploy the same exact codebase with no extra setup beyond defining a few environment variables. It took zero effort to switch from one service to another. I take no credit for this though, as it's the result of these services being designed so well, competing with each other. I only ensure that it works perfectly for your selection and provide instructions to help you get started as quickly as possible. As for other types of services, like cross-platform payment processing, push notifications, certain libraries/frameworks, etc., some of these try to lock you in, which are all avoided. Your Molecule's code covers all of this on its own so you don't have to rely on a third party. But at the same time, sometimes it can be cost effective to use a third party service, and in which case, the code is written so that adding and removing features and integrations of your own is super easy. I try to make no assumptions about what you will eventually need to add (or remove), while providing the most solid foundation possible for you.

by frx 5y ago

lowercased 5y ago

i take it to mean you're not locked in to molecule directly.

loh 5y ago
Yes, this is also the case. (Referencing my sibling reply.)

loh 5y ago

Great question. As it is now, Molecules are designed to be as independent (platform/vendor agnostic) and flexible as possible. For example, when I was trying out all the different cloud services myself, I was able to connect each of them to my git repository, and they would each build and deploy the same exact codebase with no extra setup beyond defining a few environment variables. It took zero effort to switch from one service to another. I take no credit for this though, as it's the result of these services being designed so well, competing with each other. I only ensure that it works perfectly for your selection and provide instructions to help you get started as quickly as possible. As for other types of services, like cross-platform payment processing, push notifications, certain libraries/frameworks, etc., some of these try to lock you in, which are all avoided. Your Molecule's code covers all of this on its own so you don't have to rely on a third party. But at the same time, sometimes it can be cost effective to use a third party service, and in which case, the code is written so that adding and removing features and integrations of your own is super easy. I try to make no assumptions about what you will eventually need to add (or remove), while providing the most solid foundation possible for you.