Hey HN, exciting update for content developers and DevOps folks! The Microtica Strapi Template is now upgraded to Strapi 5 (5.2.0), bringing enhanced customization, full monitoring, and automated scaling support.
This is pretty much how we started with microservices in our company, way before microservices became a thing :) We had a monolith for our document collaboration startup and there were parts of it that needed to scale, like a compare (diff) functionality. So we encapsulated this functionality into his own service.
I agree with your statement, and the post explains the pros, but also the challenges of microservices.
Our service does not depend on the project architecture, it can run with microservices, monoliths and hybrid systems just the same. It’s in our best interest to support all variates :)
There are technologies that solve one problem better than others or for example you already have modules written in Java with all business logic, integrations, security compliance (and what not) and it would take forever to adopt them in another language. Same for Python and ML. Many companies work with different tech stack and for them is also a benefit to have flexibility in that manner.
Hi sonnyp,
This is Maria from Microtica. We want to bring the cloud setup and automation (which can be complex for someone new to it) closer to developers, but not encouraging microservices over monolith or any other technology or framework. It’s up to them to choose.
The article is meant for developers that want and need to build with microservices.
True story! But the problem i see here is a bad implementation of agile that unfortunately a majority of teams have. That's why they are stuck on meetings forever and ever. Been there done that :) Agile practices (the real ones) are similar to DevOps ones, and CI/CD is a major part of them. Automation will bring you far along.
Moving towards a culture of CI/CD means that your team needs to move toward agility, so implementing agile methodology will help your team move faster into the mindset of CI/CD.
Of course the tooling to use is the most important part. Our tool Microtica (http://microtica.com) can help you automate the entire software delivery process.
Try it out and let me know what you think.
You can try out Microtica (https://microtica.com), a tool that abstracts the complex cloud setups and provides easy configurations from the UI, so you don't have to spend time on boring stuff and continue the engineering you love.
Try it out and let me know what you think.
You can create separate environments with one or multiple Kubernetes clusters. You can create a Kubernetes infrastructure for AWS in 15mins from the UI and you can also connect your existing Kubernetes cluster.
Deployment of services and monitoring through integrated dashboard, you can view and monitor deployments, pod logs etc.
There is no vendor lock-in, all resources created on your AWS account are done in a cloud-native way so you can continue operate the infrastructure without Microtica if you would like to do so.
Support for Kubernetes deployments targeting differently labeled cloud environments is in our roadmap and will be available soon.
What a great initiative, i could’t agree more. We hear very little about these kinds of products in the DevOps community.
Our product is called Microtica - a DevOps tool that enables end-to-end automation of the whole software delivery process.
Our process began about 2 years ago, when we were still working as a servicing company and struggling with broken deployments every day and spending hours on production releases. So as we are a purely technological team, decided to find a solution for our problems and automate the software integration and delivery. We started working and saw great potential in the solution, so it became an actual product that can help many more developers.
Our mission is to Power Up Developers To Work In The Cloud and bring DevOps closer to developers.