Migrating to a public cloud is never an easy task. It triggers very often questions like:
– Will the application have compatibility issues that make us stop?
– Could the private data be accessed by the owners of the cloud or by anyone else outside of the company?
Serverless means literally “without server” and it refers to a way to deploy and execute applications where the owner of the application doesn’t have to worry about the server and infrastructure used to serve it.
MLflow, the open-source platform released by Databricks in June 2018, has found a quick and broad acceptance in companies around the world.
These past months have been filled with uncertainty, we have been living a pandemic caused by Covid-19 that has changed our lives and our daily habits; working every day from home, juggling and balancing our work and personal life.
Talent is that word we say several times a day and what companies fight for, particularly those in industries where – unfortunately – it is scarce.
Over the last few years and even now, we usually hear that in order to build a microservices architecture or any distributed system, the services must be stateless. This way if we need, we can scale out adding more instances to face all the traffic that arrives. However, these systems also need to store the state in some way.
Discover how to solve the recurrent problem of floating IPs when using highly-available virtual routers in AWS. This approach will show how the new master router can claim an EC2 Secondary private IP in the failovering transition.
