With the absence of WebGrids in ASP.NET Core, developers are looking for alternatives. Today, we'll cover 3 reasons why we could use tables instead of WebGrids.
Automation isn't limited to DevOps. With Ansible, you can install what you need on remote machines, including VMs, without much manual work on your part.
You can programmatically reconfigure a log manager via Spring and load your own log4j2.xml file from a defined path, forcing your Mule app to pick the file from any location.
Using Jenkins job UI is an excellent idea if team members with little or no knowledge of Ansible need to get involved in using them to get things done.
Elasticsearch, Logstash, and Kibana (ELK) form an open source stack that has become a a leading log analysis platform to monitor, in this case, OpenStack.
Incorporate external dependencies for your Spring Boot app with a helping hand from Maven. You can package everything together, making it attractive for microservices.
Creating your own application context hierarchy can allow you, should you need to, provide different ports with different endpoints to give you some customization.
Forget the cloud, it's time to go serverless. Using AWS Lambda and API Gateway can reduce costs and overhead, and it's easy to get your Spring Boot app running on it.
If you’re looking to load your full app configuration and use MockMVC, you should consider @SpringBootTest combined with @AutoConfigureMockMvc rather than @WebMvcTest.
CORE
