I prefer to develop using IDE that’s running locally rather than a cloud-based IDE. But sometimes, developing in the cloud is invaluable. Here are two scenarios where I’ve done cloud-based development:
Sometimes, I need to develop against software that doesn’t run locally. For example, I recently tried running Oracle 23c Free - developer release. The first thing that I discovered is that the container image only supports Intel. It doesn’t run on my M1-based Mac. Consequently, I needed to run the database somewhere else.
I suppose I could have still developed locally and connected to Oracle 23c running in the cloud using SSH port forwarding.
But instead, I chose to use Gitpod.
Gitpod is remarkably easy to use.
I simply prefixed the Github repo URL with
gitpod.io/# to create a workspace.
I then used Jetbrains Gateway to connect to the workspace.
Gitpod worked reasonably well although downloading the large database image was really slow.
Another scenario where I develop in the cloud is when I need to use Windows For example, I once needed to troubleshoot Windows-specific issues with my Manning LiveProject. That’s when I discovered Windows 365 Cloud PC. I now have a Windows 11 PC that runs WSL2 and Docker Desktop for Windows. It’s accessible via Microsoft Remote Desktop and seems fairly responsive.
Microservices.io is brought to you by Chris Richardson. Experienced software architect, author of POJOs in Action, the creator of the original CloudFoundry.com, and the author of Microservices patterns.
Chris helps clients around the world adopt the microservice architecture through consulting engagements, and training workshops.
Chris teaches comprehensive workshops for architects and developers that will enable your organization use microservices effectively.
Avoid the pitfalls of adopting microservices and learn essential topics, such as service decomposition and design and how to refactor a monolith to microservices.Learn more
Chris offers numerous other resources for learning the microservice architecture.
Want to see an example? Check out Chris Richardson's example applications. See code
Got a specific microservice architecture-related question? For example:
Consider signing up for a two hour, highly focussed, consulting session.
My virtual bootcamp, distributed data patterns in a microservice architecture, is now open for enrollment!
It covers the key distributed data management patterns including Saga, API Composition, and CQRS.
It consists of video lectures, code labs, and a weekly ask-me-anything video conference repeated in multiple timezones.
The regular price is $395/person but use coupon MECNPWNR to sign up for $120 (valid until May 16th, 2023). There are deeper discounts for buying multiple seats.
Take a look at my Manning LiveProject that teaches you how to develop a service template and microservice chassis.
Engage Chris to create a microservices adoption roadmap and help you define your microservice architecture,
Use the Eventuate.io platform to tackle distributed data management challenges in your microservices architecture.
Eventuate is Chris's latest startup. It makes it easy to use the Saga pattern to manage transactions and the CQRS pattern to implement queries.
Engage Chris to conduct an architectural assessment.
Note: tagging is work-in-process
anti-patterns · application api · application architecture · architecting · architecture documentation · assemblage · beer · containers · dark energy and dark matter · deployment · design-time coupling · development · devops · docker · eventuate platform · glossary · hexagonal architecture · implementing commands · implementing queries · inter-service communication · kubernetes · loose coupling · microservice architecture · microservice chassis · microservices adoption · microservicesio updates · multi-architecture docker images · observability · pattern · refactoring to microservices · resilience · sagas · security · service api · service collaboration · service design · service discovery · service granularity · service template · software delivery metrics · success triangle · tacos · team topologies · transaction management · transactional messaging